Management infrastructure analysis for cloud migration

ABSTRACT

In a source computing system having a source management infrastructure, at least one source infrastructure management component is discovered. A description of a target cloud infrastructure having a target management infrastructure is obtained. The description includes at least one mandatory target infrastructure management component. The at least one source infrastructure management component is analyzed to determine whether at least one conflict exists with the at least one mandatory target infrastructure management component.

FIELD OF THE INVENTION

The present invention relates to the electrical, electronic and computerarts, and, more particularly, to cloud computing and the like.

BACKGROUND OF THE INVENTION

In an Infrastructure as a Service (IaaS) cloud, the capability providedto the consumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Migration is the process of moving from a source environment to a targetenvironment, such as a target IaaS cloud environment. Heretofore,migration analysis has typically only focused on operating systems (OS)and applications, not infrastructure management.

SUMMARY OF THE INVENTION

Principles of the invention provide techniques for managementinfrastructure analysis for cloud migration.

In one aspect, an exemplary method includes discovering, in a sourcecomputing system having a source management infrastructure, at least onesource infrastructure management component; and obtaining a descriptionof a target cloud infrastructure having a target managementinfrastructure. The description includes at least one mandatory targetinfrastructure management component. A further step includes analyzingthe at least one source infrastructure management component to determinewhether at least one conflict exists with the at least one mandatorytarget infrastructure management component.

As used herein, “facilitating” an action includes performing the action,making the action easier, helping to carry the action out, or causingthe action to be performed. Thus, by way of example and not limitation,instructions executing on one processor might facilitate an actioncarried out by instructions executing on a remote processor, by sendingappropriate data or commands to cause or aid the action to be performed.For the avoidance of doubt, where an actor facilitates an action byother than performing the action, the action is nevertheless performedby some entity or combination of entities.

One or more embodiments of the invention or elements thereof can beimplemented in the form of a computer program product including acomputer readable storage medium with computer usable program code forperforming the method steps indicated. Furthermore, one or moreembodiments of the invention or elements thereof can be implemented inthe form of a system (or apparatus) including a memory, and at least oneprocessor that is coupled to the memory and operative to performexemplary method steps. Yet further, in another aspect, one or moreembodiments of the invention or elements thereof can be implemented inthe form of means for carrying out one or more of the method stepsdescribed herein; the means can include (i) hardware module(s), (ii)software module(s) stored in a computer readable storage medium (ormultiple such media) and implemented on a hardware processor, or (iii) acombination of (i) and (ii); any of (i)-(iii) implement the specifictechniques set forth herein; the overall apparatus will typicallyinclude (ii) or (iii).

Techniques of the present invention can provide substantial beneficialtechnical effects. For example, one or more embodiments providetechniques for management infrastructure analysis for cloud migrationwith one or more of the following advantages:

-   -   facilitates migration of existing environments to cloud        environments having standardized infrastructure management        systems and processes (e.g., MIaaS cloud environments),    -   improves coverage of existing servers or instances that can be        migrated to such cloud environments, i.e., the fraction of        servers or instances that can be migrated,    -   decreases the risk of failure of the migration or problems after        the migration, and/or    -   where migration is not possible or needs specific preceding        measures, decreases the time needed and the risk during the        critical actual migration period (where applications are        typically shut down) by advance analysis.

These and other features and advantages of the present invention willbecome apparent from the following detailed description of illustrativeembodiments thereof, which is to be read in connection with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention;

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention;

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention;

FIG. 4 presents a high-level flow chart, according to an aspect of theinvention;

FIG. 5 presents a detailed flow chart and block diagram, according to anaspect of the invention;

FIG. 6 presents an exemplary system block diagram, according to anaspect of the invention;

FIG. 7 presents an exemplary system diagram including system states atsignificant phases, according to an aspect of the invention;

FIG. 8 shows a current server in a source environment and aftermigration to a cloud, according to an aspect of the invention;

FIGS. 9 and 10 show alternative migration approaches for the server ofFIG. 8;

FIG. 11 shows an exemplary provisioning flow, according to an aspect ofthe invention;

FIG. 12 shows instance capture, in accordance with an embodiment of theinvention;

FIG. 13 shows an adoption and adjustment process, in accordance with anembodiment of the invention;

FIG. 14 shows an exemplary screen view of a “create server” pop-up, inaccordance with an embodiment of the invention;

FIG. 15 shows an exemplary overview of adjustments in a provisioningflow, according to an aspect of the invention;

FIG. 16 presents a combined flow chart and block diagram, according toan aspect of the invention;

FIG. 17 depicts a source environment to be migrated to a targetenvironment in accordance with one or more aspects of the invention;

FIG. 18 depicts a target environment to which the source environment ofFIG. 5 can be migrated in accordance with one or more aspects of theinvention;

FIG. 19 shows exemplary phases in management infrastructure analysis forcloud migration in accordance with one or more aspects of the invention;

FIG. 20 shows an exemplary user interface in accordance with one or moreaspects of the invention; and

FIG. 21 shows non-limiting exemplary results for a small subset ofservers in accordance with one or more aspects of the invention;

FIG. 22 presents an exemplary system block diagram, according to anaspect of the invention;

FIG. 23 presents an exemplary snapshot manager, according to an aspectof the invention;

FIG. 24 presents an exemplary implementation based on a virtual imagelibrary, according to an aspect of the invention;

FIG. 25 presents an exemplary rollback to a long term snapshot,according to an aspect of the invention;

FIG. 26 is a flowchart showing steps to compute exact changes made to animage during migration, according to an aspect of the invention;

FIG. 27 is an exemplary process flow, according to an aspect of theinvention; and

FIG. 28 is an exemplary software architecture diagram of a snapshotmanagement system, in accordance with an aspect of the invention;

FIG. 29 presents an exemplary system diagram, according to an aspect ofthe invention;

FIG. 30 presents an exemplary method, according to an aspect of theinvention;

FIG. 31 presents an exemplary “swap” flow chart, according to an aspectof the invention;

FIG. 32 presents an exemplary “merge virtual resource descriptors” flowchart, according to an aspect of the invention;

FIG. 33 presents another exemplary system diagram, according to anaspect of the invention;

FIG. 34 depicts pertinent aspects of virtual machine images andinstances;

FIG. 35 shows a first embodiment of a virtual machine resourcedescriptor, according to an aspect of the invention;

FIG. 36 shows a second embodiment of a virtual machine resourcedescriptor, according to an aspect of the invention;

FIG. 37 is a flow chart of exemplary method steps for updating a targetvirtual machine descriptor, according to an aspect of the invention;

FIG. 38 is a flow chart of exemplary preparatory method steps, accordingto an aspect of the invention;

FIG. 39 is an exemplary software architecture diagram, according to anaspect of the invention;

FIG. 40 presents a standardization framework, according to an aspect ofthe invention;

FIG. 41 presents a flow of a sample offline adjustment, according to anaspect of the invention;

FIG. 42 presents an exemplary flow diagram, according to an aspect ofthe invention;

FIG. 43 presents an exemplary standardization architecture, according toan aspect of the invention;

FIGS. 44-46 shown an exemplary adjustment phase, according to an aspectof the invention; and

FIG. 47 shows an exemplary architecture, according to an aspect of theinvention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting for loadbalancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthherein.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, handheld or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and mobile desktop.

Migration to Managed Clouds

A Hardware-Infrastructure-as-a-Service (HIaaS) cloud provides bare-bonesvirtual machines as a service. It may also provide an operating system(OS) and even software, but no support is typically provided for the OSor software. A Managed-Infrastructure-as-a-Service (MIaaS) cloudprovides full-service virtual machines. The service may, e.g., includeOS patching and support for security and compliance of the OS. Onesignificant aspect of MIaaS is simpler management via: standardizationto a certain set of catalog images from which instances are generated,automatic linkage of these instances to management tools duringdeployment, and/or not giving customers administration privileges on theOS level, so that the operating systems on the instances remain as thecloud administrators configure them.

An MIaaS cloud may not naturally come with import or registrationfeatures for foreign instances, inasmuch as a significant aspect ofMIaaS is simpler management via: standardization to a certain set ofcatalog images from which instances are generated; automatic linkage ofthese instances to management tools during deployment; and, typically,not giving customers administration privileges on the operating system(OS) level, so that the operating systems on the instances remain as thecloud administrators configure them. Thus, in migrating to an MIaaScloud, it is typically not feasible to simply use P2V(physical-to-virtual) conversion on source instances, or to directlycopy already virtualized instances, and then expect them to be run oncloud hypervisors. This is so because they would not fulfill theaforementioned criteria through which simpler management is achieved inthe MIaaS cloud, and thus they would not be acceptable to the managementof the MIaaS cloud.

Furthermore, with regard to MIaaS clouds, the standard registration(i.e., making a new instance known to the general IaaS cloud managementsystems as well as the specific management systems of an MIaaS cloud) istypically inbuilt into the provisioning from catalog images.Advantageously, one or more embodiments provide a new registrationprocedure wherein foreign instances can be accommodated within migrationto an MIaaS cloud. Indeed, one or more embodiments advantageouslyprovide a system and method for rapid migration into MIaaS (and moregenerally, IaaS) clouds. The method includes transfer of the instance tothe cloud in image form; adjustments of the instance (running or inimage form) to cloud standards; and registration of the instance intocloud OSS and BSS systems (Operation and Business Support Systems).Optional additional steps address prior analysis, testing and handlingfailures, and/or starting and ending change windows and actual downtimesin order to minimize risk and outages.

One or more embodiments advantageously provide a systematic (and evenautomated) method of rapidly migrating customer instances into MIaaSclouds that does not involve a reinstall procedure. One or moreembodiments are useful with MIaaS cloud migration and are capable ofphysical-to-virtual style instance importation.

One or more embodiments enhance the ability to standardize bothinfrastructure per se and the management of such infrastructure. It isbelieved that such standardization will in turn allow reduction in IToperational costs and permit further automation. One or more embodimentsprovide techniques for migration into an MIaaS cloud which aresignificantly less expensive than techniques that require reinstall.

As noted above, one or more embodiments provide a migration techniquewith one or more of the following advantages:

-   -   significant coverage (percentage of instances and then workloads        where the method can be used),    -   low cost, which in particular is bounded by manual work needed        (in particular compared with reinstall methods)    -   short migration times (as change windows/permitted outages are        typically short),    -   low risk (e.g., of application outages beyond the planned ones),        and/or    -   predictability (i.e., workloads chosen for this migration        technique will likely succeed in it).

With attention now to FIG. 4, begin with an instance 401 in an existingcustomer environment 402 (seen in FIG. 5) which it is desired tomigrate. In step 404, transfer the instance to the cloud in image form.If this is not successful, retain the original customer version 401 andre-plan the migration; for example, retain it in its originalenvironment, or perform a classical migration into a service providerenvironment where it can remain a physical instance, or make significantchanges on the instance so that it becomes virtualizable. On the otherhand, if step 404 is successful, in step 406, carry out adjustments ofthe instance (in running and/or in image form) to ensure that itcomplies with cloud standards. If this is not successful, retain theoriginal customer version 401 and re-plan the migration; for example,virtualize it in the customer environment or a service providerenvironment without cloud standards, or an HIaaS cloud, or perform amore complex reinstall migration wherein individual software componentsare newly installed and customer data are transferred individuallyrather than within the entire image. On the other hand, if step 406 issuccessful, in step 408, carry out registration of the instance into thecloud OSS and BSS systems. If step 408 is not successful, retain theoriginal customer version 401 and re-plan the migration; for example, bythe same approaches as when steps 404 or 406 failed. On the other hand,if step 408 is successful, the result is successful migration to theMIaaS cloud 410.

Note that initial sub-steps for the cloud registration may take placebefore the adjustments or may be interleaved with the adjustments.However, from a logical standpoint, the final registration, i.e., finalacceptance of the imported instance as a cloud-managed instance, shouldbe after the end of the adjustments.

Turning now to FIG. 5, a non-limiting exemplary method is depictedtherein with greater detail. A customer environment 402 is connected toan MIaaS cloud environment 410 via a wide area network (WAN) 514 or thelike. Initially, a discovery process 518 is carried out to determineboth the physical 520 and virtual 522 instances and their configurationsin the customer environment 402. Analysis and planning is then carriedout in step 524. If the results are unfavorable, other methods, such asphysical-to-physical (P2P) migration, application reinstallation,retention of the legacy systems, and the like are pursued, as shown at526. Also, if either of steps 518, 524 indicate that remediation (i.e.,small changes to the instances to make them compatible with the cloud)is required, the same is carried out at 516 and then process flowreturns to step 518. On the other hand, if step 524 indicates thatmigration using one or more techniques disclosed herein is feasible,flow proceeds to baseline test and backup, in step 528. In step 528, asshown at 530, a set of test cases are run to prove that the sourcesystem fulfills criteria that are desired to be maintained in the targetenvironment, e.g., that it still tests correct under all of itsfunctional test cases or performance claims. This is done to ensure thatany errors already present are fixed before the migration process.Furthermore, a back-up process is carried out, as shown at 532, topermit recovery in case of any issues encountered in the migrationprocess. Preferably, before finalizing the backup 532, applications onthe physical or virtual instance 520 or 522 are stopped so that nofurther changes take place in the customer environment under conditionssuch that they would not be copied to the MIaaS cloud environment.Processing then proceeds to step 534, wherein the instances to bemigrated are captured. One or more illustrative embodiments focus onspecific aspects of migrating to an MIaaS cloud, which are largelyper-instance. As to the overall migration, it is typically done in wavesof multiple instances each, e.g., per weekend, attempting to keepworkloads or interacting instances within one wave. Such aspects havebeen disclosed, e.g., in Athey at al., System and method for objectmigration using waves, United States Patent Application Publication20110213883, Sep. 1, 2011; and Devarakonda et al., Total cost-basedmigration waves planning, United States Patent Application Publication20120109844, May 3, 2012, both of which are expressly incorporatedherein by reference in their entireties for all purposes.

As seen at 536, this instance capture step can include, for example,both physical-to-virtual (P2V) and virtual-to-virtual (V2V) techniqueswith one or more suitable tools. One non-limiting example of a suitabletool is PlateSpin® Migrate, a physical/virtual conversion tool for fastand efficient P2V (more broadly, anywhere-to-anywhere) migrations; it isavailable from NetIQ Corporation, Houston, Tex., USA; another is VMwarevCenter Converter, available from VMware, Inc., Palo Alto, Calif., USA.In one or more non-limiting exemplary embodiments, the end result ofstep 534 is a Virtual Machine Disk Format (VMDK) file.

It is to be emphasized that many product names are mentioned herein;these are intended as examples for the skilled artisan and to convey theapplicants' understanding of the best mode. They are not intended tolimit the claims unless expressly recited therein, but rather are to beconsidered exemplary of corresponding generic software products; e.g.,PlateSpin® Migrate is broadly representative of physical/virtualconversion tools.

As seen in step 538, the captured instances are then transported intothe cloud location 410 via network 514. Data 544 outside the boot diskmay be transported separately from the aforementioned vmdk file (seen at542), in particular if it is large and the data transport might startearlier. As noted at 540, the instances and data are transported throughnetwork 514 using appropriate tools to control the transfer.Non-limiting examples of such tools include the aforementioned PLATESPINtool, as well as the Softek Transparent Data Migration Facility (TDMF®)tool for data (registered mark of International Business MachinesCorporation, Armonk, N.Y., USA). Data 544 is typically not affected byspecial aspects of MIaaS cloud, i.e., it can be migrated and linked backwith the vmdk in usual ways. Thus further details about the data 544 areomitted from the figure to avoid clutter.

In step 546, functional testing is carried out on the transportedinstance(s) 554 that was restarted from the image on a cloud hypervisor.As seen at 547, this can include, for example, playing a set or subsetof test cases; this can be repeated several times between adjustments.Also, it should be noted that upon initial arrival in cloud environment410, the transported instances reside within MIaaS cloud landing zone572. If functional testing is successful at this time, processing flowproceeds to instance adjustment and adoption 556. This is a significantstep to modify the instance so that it can run in the standard MIaaSenvironment. After all adjustments, and possibly between certainadjustment steps, functional testing is repeated, as shown by thebackwards error from Step 556 to 546. After each successful functionaltest, instances can be backed up (i.e., a snapshot 552 of the instancecan be taken) as shown at step 550 (e.g., as vmdk files in an efficientinstance repository 552) for later reference, as a most recentcorrect-seeming state of the instance. If functional testing issuccessful after all adjustments 556, the transported instance(s) areinstantiated on cloud hypervisor 558 within MIaaS cloud production zone574. On the other hand, if functional testing is not successful in oneof its repetitions, processing flow proceeds to remediation step 548.The remediation process can proceed via a number of avenues. Typically,error messages will be analyzed and related to the latest changes. Theselatest changes are the virtualization and new hypervisor in the firstexecution of the functional testing 546. In subsequent executions, theyare the changes by the adjustments since the previous execution of thefunctional. For this, it may be useful to refer to a snapshot 552 of theinstance before these last changes. If remediation of these errors isnot successful (which might be determined by a rerun of the functionaltest), flow returns to step 528, i.e., the migration of this instance isstopped (at least for the moment) and the backup is used to restore thesource instance 520 or 522 in the customer environment 402. Whenremediation is successful, the processing proceeds as if that functionaltest had succeeded at once, i.e., with the first or next adjustment or,if all adjustments are done, with instantiating the instance on cloudhypervisor 558 within MIaaS cloud production zone 574.

Within the instance adjustment and adoption step 556 the instances onhypervisor 554 are adjusted to cloud delivery standards and adopted intothe cloud BSS and OSS, as seen at 568. As seen at 570, this processemploys provisioning flows extended by adjustment subflows. For example,the standard provisioning flow of the MIaaS (i.e., for instances chosenfrom the cloud catalog, rather than migrated) may register a newinstance in an asset management system, a monitoring system, and startbilling and accounting for it. This functionality can be reused from thestandard provisioning flow. On the other hand, the standard provisioningflow may not install a certain monitoring agent that the MIaaS cloudrequires on the normal instances because they would be preinstalled inthe cloud catalog images. Hence installing this agent would be part ofthe special adjustment flows. Similarly, an update of the securitypatches to the level that the cloud catalog images have may be an extrastep in the adjustment flows. When the functional testing after alladjustment steps finally has successfully completed, as noted,instantiation occurs on cloud hypervisor 558 within production zone 574.

In one or more embodiments, the landing zone is a special zone added formigration to an MIaaS cloud, because when the instances are firststarted on a hypervisor the MIaaS cloud environment (see item 554) inorder to test and adjust, they do not yet fulfill cloud standards andthus the normal cloud management cannot handle them. They may also notfulfill the security standards that the OS management in the cloudprovides and assumes. For this reason, one may physically separate thelanding zone 572 and the production zone 574, at least by usingdifferent servers to host the hypervisors, and separate them byfirewalls that only let the controlled information through as indicatedby the two arrows between the zones. Also the storage systems may beseparate. Another advantage of physical separation is that the cloudmanagement systems such as capacity and performance management thendon't have to deal with hypervisor(s) that are partially filled withnormal, managed cloud instances and partially with as yet unmanageableimported instances. However, it is also conceivable to use logicalseparation, i.e., trust the cloud hypervisors to not let the potentiallyinsecure imported images impact the others, and to extend the cloudmanagement systems to deal with partitioned hypervisors.

Once the pertinent migrated instances are instantiated on cloudhypervisor 558 in production zone 574, user acceptance testing 560 maybe conducted, for example, to verify that performance is equivalent tothe baseline. If not so, remediation is carried out at 562, to correctthe instances on hypervisor 558. This remediation process can make useof instance repository 552 or alternate techniques 526 as appropriate;if this happens, the instance should be removed from the production zone574 again until it is remediated. The test cases in the user acceptancetest 560 should preferably be identical to those in the baseline test528. They often cover multiple instances together if the user-relevantfunction is performed by multiple instances, e.g., a web server, anapplication server, and a database. In contrast, the functional test maybe per instance only. When testing 560 is successful, cut-over iscarried out in step 564, taking into account any customer domain nameserver (DNS) changes or the like, as seen at 565. Upon completion ofcut-over, as seen at 566, the migrated instances operate in the MIaaScloud production zone in a business as usual (BAU) manner.

In FIG. 5, it will be appreciated that in one or more exemplaryembodiments, steps 516, 528, and 560 are in the scope of the customerwhile steps 518, 524, 526, 534, 538, 550, 556, and 564 are in the scopeof the cloud services provider. Steps 546, 548, and 562 are of a mixednature between both parties.

FIG. 6 shows an exemplary system diagram. Customer environment 402includes one or more source instances 684 (corresponding to the initialphysical or virtual instances 520 and 522 in FIG. 5) and a transferagent 682. Network 514 provides connectivity between customerenvironment 402 and MIaaS cloud environment 410. Environment 410includes landing zone 572, production zone 574, and management zone 680.Transferred instances 686 reside within landing zone 572 (element 554represents an instance running on a hypervisor). Final target instances688 reside within production zone 574 (element 558 represents aninstance running on a hypervisor). Cloud management zone 680 includes anumber of management components. Transfer core component 690 carries outinstance transfer of source instance 684 to transferred instance 686,working in conjunction with transfer agent 682. Adjustment component 692orchestrates the adjustment process discussed with regard to landingzone 572 in FIG. 5. Registration component 694 registers the adjustedinstance into the normal management system of the MIaaS cloud, hereshown by the BSS and OSS 696, 698. Cloud OSS and BSS systems (Operationand Business Support Systems) 698, 696 provide input for step 556, asseen at 568. The normal function of OSS and BSS in an MIaaS cloud is tomanage instances in the production zone 574. However, the landing zone572 also needs at least a minimal OSS, e.g., for capacity management andthus finding a suitable place (server and storage with enough capacity)when a source instance 684 is coming in. If the landing zone isphysically separated from the production zone, then at a more detailedlevel the OSS may be separated too. In any case, the adjustmentcomponent 692 and registration component 694 prepare the instance forreception into the OSS 698 so there is at least an abstract connectionin the sense of them needing knowledge about the OSS requirements. A BSSfor the landing zone is typically not necessary because in the landingzone, the instances are controlled by the migration process, and not yetvisible to the customer or end user.

FIG. 7 shows system states at significant points in time (i.e., duringsignificant phases); namely, initial state 707, after transport 709, andafter cutover (cloud BAU) 711. In state 707, the customer's existingmanagement tools 703 are managing both the physical 520 and virtual 522instances in the customer environment 402. The same are stored instorage 705 (e.g. as described with respect to backup step 528 and 532,but also the plain external storage of the instances if that is outsidethe servers, e.g., on a storage-area network or a networked filesystem). The instances are captured. As discussed above with regard to536, this instance capture can include, for example, bothphysical-to-virtual (P2V) and virtual-to-virtual (V2V) techniques withone or more suitable tools; transport can be via WAN 514 (which couldinclude, for example, the final virtual private network (VPN) (used forcommunication between the customer and cloud environment during normaloperation after migration is complete), or a temporary line) or bytransfer of physical media. In one embodiment, cloud environment 410includes cloud provider hardware and hypervisor 554 in cloud landingzone 572, cloud provider hardware and hypervisor 558 in cloud productionzone 574, and shared storage 701. This embodiment is a compromisebetween full physical separation of landing zone and production zone asdescribed above, where even the storage would be separate, and solelylogical separation, where even the hypervisors would be shared and thezone separation would be enforced by the hypervisors—both of those arealso among the possible embodiments. One benefit of this mixedembodiment is that the final transfer of the instance from landing zoneto production zone does not need to copy the data; only the ownership ofthe storage volume(s) belonging to this instance is changed to theproduction zone.

After transport, as seen at 709, physical and virtual instances 520, 522are now both virtualized on cloud provider hardware and hypervisor 554in the landing zone 572, as seen at 720, 722, respectively, and therethe adjustments and testing take place. Migrated data is stored inshared storage 701. Preferably, the source instances 520, 522 have beenshut down before the transfer, as explained above with respect to thebackup 528. One extreme case is that they are not running at all(physical server switched off for 520; instance removed from hypervisorfor 522), but typically one would only stop the services on them (sothat no changes are made that would be lost when business-as-usualresumes in the cloud production zone). If read-only services can bedistinguished, e.g., browsing on informational web pages, those can keeprunning. Furthermore, one would typically retain the instances 520 and522 still in the customer management tools in case migration fails, sothat operation in the customer environment could resume quickly.

After cut-over, during the cloud BAU (business as usual) state, as seenat 711, physical, virtual, and storage resources 520, 522, in thecustomer environment 711 are shut down, and storage 705 used by them isreleased. Meanwhile, any required adjustments and remediation have beencompleted, as described with regard to FIG. 5, physical and virtualinstances 520, 522 are now both virtualized on cloud provider hardwareand hypervisor 558 in the cloud production zone, as seen at 724, 726,respectively. Migrated data is still stored in shared storage 701 inthis embodiment of partial physical separation of landing zone andproduction zone. With full physical separation, there would be twodifferent storage systems, one in the landing zone and one in theproduction zone, and the data would reside on the former in phase 709and on the latter in phase 711. BAU cloud processing occurs undercontrol of cloud OSS and BSS systems (Operation and Business SupportSystems) 698, 696 seen at 568. The customer management tools 703 may beprovided with an interface to production zone 574. However, thistypically only concerns those specific tools that manage on theapplication layer, while tools that perform OS-level functions (such asOS performance management) have been replaced by the cloud OSS in 568.For example, the instance (initially 520 or 522, then 720 or 722,finally 724 or 726 may contain a database, and the customer may have adatabase management tool as part of 703. An MIaaS cloud (in contrast toa PaaS cloud) typically does not perform database management. So thecustomer database management tool gets a link to this database oninstance 724 or 726. This approach uses the normal way in whichcustomers of the cloud link to their instances of the cloud, e.g., aVPN; it is not in conflict with any zoning or administration constraintsof the MIaaS cloud. It should be noted that FIG. 7 shows an exemplarytime of one hour to two days to move from initial state 707 to “aftertransport” state 709 and an exemplary time of two hours to one day tomove from “after transport” state 709 to “after cutover cloud BAU” state711. These values are intended to provide helpful example for theskilled artisan but are not intended to be limiting.

One or more embodiments thus provide a method for migrating an instanceinto a cloud, including transferring the instance to the cloud in imageform; adjusting of the instance to cloud standards; and registration ofthe instance into cloud management systems. In some cases, registrationis done by a variant of the cloud provisioning method in which pickingup a catalog image is replaced by picking up a transferred instance. Insome embodiments, cloud management systems include an operationalsupport system and a business support system. In some embodiments, cloudstandards include one or more of security standards, infrastructurestandards, patch management standards, and infrastructure managementtool standards.

Furthermore, in one or more embodiments, adjustment is done by aworkflow defined in a workflow engine. In some cases, one or moreadjustments are done in the workflow by special tools such as a patchmanagement tool.

In some embodiments, before the transfer step, analysis is carried outon the instance to determine whether it is suitable for the cloud andthe given migration method, and only suitable instances are consideredfurther. Furthermore, in some embodiments, tests are carried out at oneor more of the times before the transport, after the transport, betweendifferent adjustments, after adjustments, and after migration, andremediation and/or back-out occur if one or more of the tests fail. Insome cases, multiple instances are treated as a whole in one or more ofthe decisions to migrate (i.e., whether suitable for cloud as mentionedearlier in this paragraph) and/or in the tests and back-out decisions.

Furthermore, one or more embodiments include discovery, actual handlingof failures, starting and ending change windows and actual downtimes,detailed interleaving of adjustment and registration, and/or thecut-over step.

Certain terms employed herein will now be defined:

IaaS clouds: Infrastructure-as-a-Service is a common term for cloudsthat primarily offer their users virtual machines (VMs), rather thanalso software on the VMs (referred to as PaaS, platform-as-a-service) oreven software without access to the VMs (referred to asSoftware-as-a-Service) or business processes (BPaaS).

The following subdivision of IaaS clouds are introduced herein:

HIaaS cloud: A Hardware-Infrastructure-as-a-Service cloud providesbare-bone virtual machines as a service. It may also provide anoperating system (OS) and even software, but typically no support isprovided for the OS or software (e.g., Amazon Elastic Compute Cloud(Amazon EC2) available from Amazon Web Services LLC Seattle, Wash.,USA).

MIaaS Clouds: A Managed-Infrastructure-as-a-Service cloud providesfull-service virtual machines. The service may, e.g., include OSpatching and support for security and compliance of the OS (e.g., IBMSmartCloud Enterprise+ also known as IBM SCE+, cloud environmentavailable from International Business Machines Corporation, Armonk,N.Y., USA)

Instance: An operating system instance together with all softwarerunning on this operating system. It may be physical (i.e., directlyrunning on a server) or virtual (i.e., already running on a hypervisor).

Source instance: Instance as it is running on the source side, beforemigration.

Image: File representation of an instance.

Catalog image: Image in a cloud catalog, to be used if new instances arecreated in the cloud from scratch, rather than by rapid migration.

Provisioning: This is the standard mechanism of ordering VM instances inan IaaS—the user orders a VM from the catalog, and the correspondingactual image is instantiated into a running instance.

Reinstall migration: From the point of view of an MIaaS cloud, thestandard way of moving an application into same is to first provision acatalog image, and then to reinstall necessary software components,source code, configurations, and data into it. However, this istypically a very time-consuming and costly process.

Image-based migration: Image-based migration uses customer instances formigration of the application to the cloud. In classic virtualization,image-based migration is a standard (P2V) and can be very fast. However,because the image generated directly from the source instance does notenable the management part of the MIaaS cloud, heretofore, image-basedmigration has not been feasible with MIaaS clouds.

Rapid migration to MIaaS cloud: An extension of image-based migration,in accordance with one or more embodiments, which can handle thechallenges of image-based migration, in an MIaaS cloud.

Referring now to FIG. 8, with regard to rapid migration, the skilledartisan will appreciate that there are typically many things on a server802; for example, middleware or other off-the-shelf software (MW) 804,806; Infrastructure software (“Infra”) 808 such as monitoring andprovisioning agents; custom code 810; and/or scripts 812, e.g., forbackup, scheduled cleanup tasks, data transfers, and the like. Ofcourse, the server includes hardware 820 and an operating system (OS)822 (typically with registry and users (not separately numbered to avoidclutter)). As seen at 824, the current server may be a simple physicalserver with an OS, data, and software, or may already be virtualized viaa suitable hypervisor. Middleware such as 804, 806 typically hasconfigurations 814, data 816 (e.g., databases), code 818 (e.g., SQLscripts), and is often associated with other scripts (such as databaseadministrator scripts). Most of these do not need to be in standardlocations. We have found that it is typically quite difficult toautomatically find everything that is related to the running instanceseven of very common standard software such as web servers and databases.

In one or more embodiments, rapid migration in accordance with aspectsof the invention is believed to be particularly suitable for aninfrastructure-only migration, and for unchanged major OS version, i.e.,when the goal is to get to an MIaaS cloud, but not to make other majorchanges. As seen at 802′, when the “same” server is moved into thecloud, it now runs on cloud hardware 830 and hypervisor 832 is employed.Other than that, there are limited changes:

-   -   small updates in the operating system (now OS' 822′)—namely,        different drivers, cloud provider user IDs, IP address    -   somewhat different infrastructure software (cloud management        tools—now Infra' 808′)

One or more embodiments make use of the insight that it is advantageousto update the few things that change, rather than individually pick upall those that don't change, with a risk of forgetting something.Referring now to FIG. 9, the OS 822; MW 804 (including itsconfigurations 814), 806; infrastructure 808, code 810, scripts 812,code 818, and data 816 are kept together, moved into the cloud, and thensmall changes are made to OS 822′ and infra' 808′. Advantageously, inthis approach, if anything does not work in a change, it is most likelyonly the cloud service provider-side infrastructure management (as thatgets newly added), not the application (which remains essentiallyuntouched). Of course, this assumes in the first place that theapplication can in fact be virtualized. The skilled artisan will ofcourse appreciate, given the description herein, that extra care shouldbe taken, e.g., that the new resources of the server additionallysupport the cloud management agents.

FIG. 10 shows an alternative approach (reinstall/re-platform) that doesnot employ the aforementioned rapid migration technique. This is whatthe MIaaS provider would typically expect its users to do, but is oftennot feasible in terms of time and money. In this figure, afterprovisioning an instance with an operating system OS' 808′ similar tothe original OS 808 from the cloud catalog, and freshly installing theoff-the-shelf software, essentially everything is moved one by one.There is some current tooling available along these lines, but it isonly available for a small subset of possible off-the-shelf software,and almost no tooling is available to move extras like scripts, code,etc., nor even just to list it all for subsequent transfer. It is alsonot in any way an easy option to move “everything else” afterinstallation—OS, applications, and configs/data/custom code are highlylinked, both in file systems and in OS data structures such asregistries, in particular on WINDOWS.

Consider now core options of interleaving adjustments and registrationin rapid migration, i.e., in the new technique described along FIGS. 4-7and 9, i.e., Steps 406 and 408 in FIG. 4, or elements 556, 558, 570 inFIG. 5. Purely by way of example and not limitation, consider inparticular several core options to add a registration flow for importedinstances to an MIaaS cloud:

First option: Run the provisioning flow for the closest related catalogimage (which the analysis and plan phase 524 decided that the instancewill be adjusted to simulate). Then swap the instance generated from thecatalog image for the imported instance, on which most adjustments havebeen already done (e.g., additional patching, security complianceadaptions). This may be done on the image file level for suspendedimages. Some adjustments on the imported instance may be needed afterthe provisioning, e.g., if the provisioned instance had some identity(such as an IP address) that now needs to be transferred to the importedinstance because the MIaaS management requires it but cannot tell it inadvance. Note that such swapping and post-swap adjustment cannot be doneby a user of an unmodified MIaaS cloud; it needs special authorizationand, in order to be reasonably efficient and secure, automation toolingto be added to the MIaaS management system.

Second option (see FIG. 11): Modify the provisioning flow so that itstill performs most of the registration work, but at some point picks upthe image of the imported instance instead of the catalog image. If theprovisioning flow performs real-time actions on the images (e.g., agentinstalls) those can also be reused (rather than being done inadjustments before the registration flow). If possible, retain thecommon parts of the provisioning flow and the new registration flow asactual common components (common subprograms, sub-workflows, or thelike)

Referring now to FIG. 11, depicted therein is an exemplary provisioningflow in an MIaaS cloud environment (IBM SCE+ is one non-limitingexample). In step 1101, a customer accesses customer portal and servicecatalog 1110, which are part of the BSS (568, 696) of the MIaaS. In oneor more embodiments, “Adoption” or “import” is a new service type in thecatalog 1110 (compared with the MIaaS cloud as designed without the newrapid migration mechanism) and is available for certain roles. In somecases, this aspect can be implemented by a relatively small change in anexisting user interface (UI) of the MIaaS cloud. Appropriate parametersmay be passed through to a provisioning process described below. Theservice request may involve, as shown, a service catalog; receipt of arequest, fulfillment of the request, and updates to virtual machineprovisioning status. In some cases, server resource usage status isshown during use.

In step 1102, provisioning is carried out with provisioning engine 1112.MIaaS Provisioning can include receiving the request from the portal1110; using the image to create an instance; the creation of a virtualserver including provision of resource requirements such as CPU, memory,disk, hostname, IP address, and/or sub-nets; installation of agents formanagement, configuration of agents, connection to virtual local areanetworks (VLANs); and/or server validation. One or more embodiments,with regard to registration of imported images as modification to such aprovisioning flow, pick up the imported instance instead of a catalogimage in the sub-step “Use image to create instance” of step 1102. Hencethis sub-step becomes the creation of an instance 558 in the productionzone from the imported instance, in relation to FIG. 5. If the landingzone is physically separated from the production zone, this involvesactually copying the adjusted instance 554 from the landing zone to theproduction zone. If the landing zone is virtual, that instance may evenbe kept in place, but an address (name, pointer) of it is now given tothe provisioning flow.

In one or more embodiments of the rapid migration method, duringcreation of the virtual server, the exact CPU, memory, and disk arecreated as in the imported instance or a plan from Step 524 (because thecloud may not have images with the exact resource sizes as the importedimage, the next-larger sufficient size will typically be chosen). Someembodiments employ dual-homed instances which have a cloud servicesprovider internal IP address (for cloud management system of the MIaaSto access the instance) and a customer-facing customer address; this istypically different from the old IP address of the imported instance,and thus the address on that instance must be changed to thecustomer-facing address that the cloud management system provided.

It should be noted that words such as “must” or “shall” discuss itemsthat are mandatory in an exemplary embodiment, but may be optional inother embodiments. No limitation to the claims is intended unlessrecited therein.

In some cases, with regard to the installation and/or configuration ofagents, a new flow is provided for handling prior agents such as, forexample, a performance monitoring agent or a backup agent, if the MIaaScloud uses different agents or tools for the same purpose. Concrete,non-limiting, examples include Altiris products available from SymantecCorporation, Sunnyvale, Calif., USA, and products available from NetIQCorporation, Houston, Tex., USA. The handling of such agents mightinclude, for example, uninstall or an authorization reduction fromadministrator rights to user rights, or a policy change in the tool.Alternatively, however, this flow can be done as adjustments in thelanding zone before even starting the provisioning flow.

In step 1103, the virtual server is created. In the non-limiting exampleof FIG. 11, this can be carried out using the virtualization manager1116 for INTEL technology (e.g. making use of VMware ESX VMs (VMware,Inc., Palo Alto, Calif., USA) as shown at 1120) and/or thevirtualization manager 1118 for POWER technology (e.g. making use of IBMPowerVM logical partitions (LPARs) as shown at 1120; InternationalBusiness Machines Corporation, Armonk, N.Y., USA). In either case,suitable storage, such as storage area network (SAN) storage 1114 can beemployed. Other types of technologies can be employed in otherembodiments. This step can include taking the request from theprovisioning engine 1112; allocating appropriate computing resourcessuch as CPU, RAM, disk space, and so on; copying the image over; placingsame on the physical server; booting the operating system andmiddleware; and/or applying IP and hostname. In some embodiments of theadoption of such a flow for registration in rapid migration, a furtherstep includes preparing custom access for tests. In MIaaS provisioningwithout migration, such a test is not needed because this is a standardcatalog instance, but here, an imported, adjusted instance is beingdealt with, and it will be appropriate to carry out the user acceptancetest 560.

In step 1104, server validation is carried out with the aid ofprovisioning engine 1112. This can involve, for example, checking forcorrect installation and configuration of management agents; a securitysweep (as to ports, password policies, and the like); checking validityof user IDs; running a health check; documenting server information intoa master database; and/or reporting to a suitable management tool suchas the IBM Service Delivery Manager (SDM) available from InternationalBusiness Machines Corporation, Armonk, N.Y., USA.

One or more embodiments advantageously employ automation for typicalmodifications in the adjustment workflow, so that these tests (e.g.,security sweeps) typically do not fail—in fact these validation steps ofthe MIaaS cloud can be seen as the primary specification of whatadjustments must be made in migration into this MIaaS cloud.

Step 1105 includes a final validation more on the BSS layer, in contrastto the OSS layer validation in Step 1104. This can include, for example,the SDM checking the validation report; confirming requests; approvingrelease of the VM (i.e., instance) to the customer; the cloud servicesprovider adding customer users to the servers (if not already there);and/or providing server access to the customer. In some embodiments, inmigration the access will be provided earlier for testing, as describedfor step 1103

Exemplary non-limiting details will now be provided regarding a numberof steps that may be carried out in one or more embodiments.

Discovery (Step 518)

In some embodiments, with regard to a first run—before firsttransformation planning, standard tools such as IBM Tivoli ApplicationDependency Discovery Manager (TADDM) available from InternationalBusiness Machines Corporation, Armonk, N.Y., USA, the IBM Galapagostool, and the like, can be run well in advance of the actual migrationon the production systems. With regard to the IBM Galapagos tool, see,e.g., Galapagos: model-driven discovery of end-to-endapplication-storage relationships in distributed systems, IBM Journal ofResearch and Development archive, Volume 52 Issue 4, July 2008, Pages367-377 and Nikolai Joukov, Birgit Pfitzmann, HariGovind V. Ramasamy,Murthy V. Devarakonda: Application-Storage Discovery; SYSTOR 2010,Haifa, May 2010. In some cases, these tools can be preinstalled on anappliance (a small physical server) for easy installation into thecustomer environment 402. This approach unifies these tools, customerinputs, and loading from certain available customer repositories. In atleast some cases, the cloud services provider can ask about additionalaccess to complete file system copies of instances, in particularvirtual instances 522, already (but nothing in the process relies onthat).

In some embodiments, with regard to a second run, the same is carriedout in a per wave fashion. That is to say, there is discovery againlater, per wave, preceding migration by (for example) a couple of weeks.The same tools can be used, often with additional options and plug-insto obtain more details. After this second run of discovery 518, in oneor more non-limiting examples, a change freeze is implemented for codeand configurations, so that the subsequent steps can rely that theinformation from discovery is current.

Analysis and Planning (Step 524)

This phase decides whether business applications are capable of beingmigrated to one or more MIaaS cloud environments (SCE+ is a non-limitingexample) and which migration method to use. This is assumed to beintegrated with general migration planning tools (for migrations and ITtransformations of other types than to an MIaaS) that an organizationmight have, e.g., the IBM Migration Factory. Within this tool, themigration to MIaaS should share information such as fornon-virtualizable software, software-OS-compatibility, and upgrade costswith non-cloud migration. Those might, e.g., be available as statictables in a database underlying a planning appliance. One significantcriterion for what workloads go into the path of rapid migration to anMIaaS cloud is that they already have the correct major OS version. Forexample, if the image catalog of an MIaaS cloud contained only imageswith Windows 2003, 2008, and Red Hat Enterprise Linux (RHEL) 5.6 asoperating system versions, the planning might decide to only use rapidmigration to this MIaaS cloud for source instances 520 or 522 thatalready have one of these 3 operating systems, or at most additionallyRHEL 5.1 to 5.5 (so that a minor upgrade is needed in adjustment). Ifthere is non-virtualizable software on an instance that has one of theseoperating systems or other exclusion criteria (special hardware,potentially clusters), this instance still has to go to a differenttarget environment, or be significantly remediated first (step 526). Insome cases, regulated workloads are not migrated, but this is notintended to limit the scope of the claims unless expressly recitedtherein. In some cases, this aspect is implemented via extended statictables and discovery to minimize potential issues; although the skilledartisan, given the teachings herein, will appreciate that standardanalysis techniques that analyze the possibility of physical-to-virtualtechniques, suitably modified, can be employed to implement this aspect.

In one or more embodiments, this phase also includes analyzingcompatibility of the patch status of the source instance with standardsof the MIaaS cloud; this is specific to migration to MIaaS cloud.

In one or more embodiments, this phase also includes the selection of animage size. In at least some cases, simply retain the size, unless it isnecessary to increase it to fit the new agents in that have to beinstalled during adjustments. If the MIaaS cloud only allows certainfixed image sizes (in terms of CPUs, memory, disk storage etc.), it maybe necessary to resize the image later to the next larger suitable size;however, this should not be an exclusion criterion.

In one or more embodiments, this phase also includes wave planning,i.e., grouping servers that will be migrated together. This can becarried out, for example, using standard migration tooling (such aspectshave been disclosed, e.g., in the aforementioned United States PatentApplication Publications 20110213883 and 20120109844); usingdependencies, locations, subnets, and so on; optionally, an attempt maybe made at this stage to free hardware and the like. It should be notedthat in the general case, there is no guarantee that there will not becross-wave dependencies—some environments are too interlinked.

In at least some cases, security zones should be planned in this phaseand certain cloud pools (i.e., groupings of instances that the cloudprovides) and the like should also be planned. Refer to the discussionof the request GUI below with regard to FIG. 14.

Baseline Test and Backup (Step 528)

In the baseline test, the customer (or the migration team) performs allthe tests that they will also apply after migration, to make sure theexisting system passes all those tests. In one or more embodiments, theactual tests are the same as in user acceptance testing (UAT). This caninvolve, for example, some UAT tests that write into databases or thelike such that they cannot be performed on production servers (e.g.production zone 574); test servers from the customer environment maythen be used for the baseline test can then be employed, although theactual workload deployment there may be simpler than the productionconfiguration.

In at least some cases, backup is performed by the customer, and thecustomer validates that it worked, as instance capture can causeproblems. In some cases, the cloud services provider does not makebackups on the customer side.

In some cases, the customer may carry out additional steps in thisphase. For example, to enable the instance capture processes discussedjust below, there are other things the customer should do, inparticular:

-   -   ensure there is a change freeze for their own developers;    -   give the migration team (which can be in-house, from the cloud        services provider, or another party) root rights on the instance        to be migrated; and    -   give the migration team a realistic change window for the        migration, as physical-to-virtual (P2V) counts as a change, even        in cases where it's run in the background.        Instance Capture

Multiple variants can be employed for this step. Refer to FIG. 12.Non-limiting examples will be presented, all of which are valid forarbitrary transfers to virtualized environments:

-   -   If the source instance 520 in the customer environment 402 is        still physical, a P2V operation (physical-to-virtual) will be        involved as shown at 536. There are standard tools for this,        e.g., the aforementioned PlateSpin tool, and the VMConverter        tool available from the aforementioned VMware, Inc.    -   If there are multiple drives, they may be treated by the same or        different tools. A data drive transfer may, e.g., start earlier        than a boot drive transfer and be done with a resynchronizing        tool such as IBM Softek TDMF software, to accommodate large        amounts of data with short change windows.    -   If a P2V operation is needed, it might be local (i.e., first        creating a virtual machine or image in the customer environment        402) followed by transport; or it might be integrated with the        transfer, i.e., the new virtual machine or image file        immediately exist in the target, i.e., the “landing zone” 572.

Significant customer-facing aspects in one or more embodiments include:

-   -   The migration team needs to get root/admin rights on image    -   If non-boot volumes are present, and transferred by a        resynchronizing tool as described above, the tool must be        installed beforehand.    -   A change window should start here at the latest    -   Applications are typically shut down during P2V time    -   There should be a “starting zone” where the captured images go        awaiting transport, in cases where all the transport is over a        WAN 514 (at least for large images, small ones may go directly        via the PlateSpin tool, for example).

Instance capture may include a suitable shut down process. In someembodiments, the enterprise applications (aka workloads) are shut downbefore a potential P2V step (if this has not already done duringbackup). This means to shut them down from the point of view of users—ina multi-component workload, it does not necessarily mean shutting allcomponents down; e.g., just the frontend web server might be disabled.It is safer not to even have any software components running during thecapture step (cold P2V), but it is possible with the given tools to doit while things are running (warm P2V). The application owner, in one ormore embodiments, defines what to shut down, and preferably carries outshut down, because the migration team, being tasked withinfrastructure-level tasks, may not have full insight into this.

Instance capture may include, for example, the P2V step for physicalservers. For already virtualized servers, in particular on VMware,little is required in this step. In one or more embodiments, after theend of P2V, changes are no longer allowed on the source (if this has notalready been disallowed during backup), as they would not be transferredto the target. That is, typically the entire source instance is now shutdown to ensure this. If the instance was already virtualized, it is shutdown either before the image to be transported is finalized, or in anintegrated transport, at the latest before the final resynchronizationwithin that transport.

If a capture step is separate from the transport step, a “starting zone”should be provided for the captured instances, i.e., storage space forthem that is close to the transport technology.

Transport to Cloud Services Provider (Including Data)

Data transfer may by over a network or via a physical medium, dependingon network bandwidth and physical distance. This can be done, in somecases, with a resynchronizing tool (one example is IBM Softek's TDMF),especially for large images or for non-boot drives. A tool such as TDMFshould be installed beforehand, and if there is a large data set asnon-boot drive, background data transfer may be started earlier than theP2V. If it is certain that the boot drive does not contain normal“data,” in at least some cases, it may be feasible to only do a changefreeze on that, i.e., only resynchronize other drives. Due attentionshould of course be given to customer acceptability.

There should be sufficient bandwidth to the landing zone, typically muchmore than the standard WAN connection to the MIaaS cloud as it will beneeded in the business-as-usual phase 711. In some case, special opticallines may be employed. It is possible to add WAN optimizers to same(such as those available from Riverbed Technology, San Francisco,Calif., USA). In at least some embodiments, sizing should be for themaximum wave load, rather than average. Another option is to usephysical storage media such as a high density SATA (Serial ATA (SATA orSerial AT Attachment)) disk array and to transport it by courier orsimilar means. By using a resynchronizing tool to copy data onto them,resynchronization via the network is possible after that.

Landing Zone

One or more embodiments employ a “landing zone”, i.e., an environment inthe same data center as the ultimate cloud place of the particularinstance, and with the same hardware and hypervisor version (e.g., sameESX version for VMware ESX VMs), where such imported instances can berun. In some cases, with regard to the initial transport, if it was doneseparately for an image file, all that is needed is enough storagespace, as for any transport. However, at the latest for the firstfunctional test, a runtime environment for the imported instance shouldbe available. In one or more embodiments, there will be at least onelanding zone per data center, as further WAN transfers are not employedonce an instance is transferred to the cloud services provider.Potentially there may be even more landing zones, in particular if thedata center contains multiple physically separated or separately managedproduction zones; then there can be one landing zone per productionzone.

Any security zoning of the customer that needs to be replicated can bedone virtually, i.e., via the cloud service provider's VLANs andfirewalls, but unless the customer requires physical separation ofcertain security zones also in the production environment (not usual inclouds), the instances can all land on the same hardware, controlled bythe same management software.

As discussed before, the entire landing zone may be physically orvirtually separated from the (corresponding) production zone. Exactplacement and address are pertinent considerations in one or moreembodiments. In the case of virtual separation, one preferably importseach instance physically close to where it will stay after registration,so that no additional copying is needed. E.g., if the production zone issub-structured into several units, where, e.g., each unit is controlledby a VMware vCenter Server(s) or a TSAM (IBM Tivoli® Service AutomationManager software available from International Business MachinesCorporation, Armonk, N.Y., USA), and the landing zone is virtual evenwithin such units, the instance can be maintained on the same physicalserver and storage when transferring it from the landing zone into theproduction zone. For example, the instances still belonging to thelanding zone can have a flag “tolerated,” so that TSAM knows they arethere but not yet managed in the production zone sense. However, if foradditional security and lower complexity, the landing zone resides inother units than the production zone, then actual copying is needed, andthe registration flow, which is largely executed in the production zone,must be given an address of the instance in the landing zone and theauthority to copy from such addresses (e.g., by opening a special portin a firewall).

Functional Testing

After transport to the cloud services provider, testing should becarried out to verify that the P2V and transport worked correctly. Forthis, standard methods employed in non-cloud P2V transformation can beused, as so far no MIaaS-specific adjustments have been made. A minimumtest is that the instance can be started at all. In some cases, thistesting may be limited to OS, storage, and the like; in other cases, itmay be extended to whether software or even the entire businessapplication still works. In some cases, there may be a list of what wasrunning from the time of shut-down. In some cases, a capability isprovided by the migration team for automatic restart. On the other hand,in some cases, this is handled by the customer. The test is typicallynot identical to the complete baseline test.

Backup/Snapshot Instance Before/During Adjustment

Directly after the transport into the cloud services provider, andoptionally between any steps where tests are performed, a backup may bemade (with a VMware snapshotting technique) to enable easierremediation. However, in particular with mature processes, one may alsodecide not to make these intermediate backups in order to save time inthe most common correct case. Backup is particularly useful before/aftersteps that involve a human decision, while automated steps can easily bere-done from the first backup.

Remediation 550

In at least some cases, this is a largely human step. If something goeswrong, it typically needs debugging. If too much difficulty isencountered, the instance and possibly the entire business applicationshould be taken out of the current wave, i.e., the current weekend's (orother pertinent time period's) migrations. It is desirable to documentsuch cases well, so that in the future such cases can be caught in thephases of Discovery 518 and Analysis & Planning 528.

Instance on Cloud Service Provider's VMware ESX Virtual Machines or theLike

At this time, start the adjustment flow with the running instance thatjust passed functional testing.

Adoption and Adjustment Sub-Flow 556

In at least some cases, adoption (referred to herein interchangeably asregistration) and adjustment are carried by small modifications of theprovisioning flow as discussed above in reference to FIG. 11. For a moregeneral view, concentrating on the steps specific to migration (FIG. 11showed the “non-migration” steps and the specific migration steps werediscussed in the text) reference should be had to FIG. 13. In step 1302,determine whether any pre-adoption adjustments are needed or desired,i.e., adjustments that are done before and separate from the anyregistration steps, i.e., steps that involve the MIaaS Cloud BSS and OSS568. This determining may refer as needed to a decision document or thelike as output by the Analysis and Plan step 1306. In step 1304, startthe adoption flow with appropriate instance parameters (and cloud zone)from analysis and planning step 1306. In step 1308, the portal flowpasses the “adopt” parameter through, i.e., a parameter that indicatesthat the flow variant needs to be executed where an imported instance isregistered. (This flow modification will be implemented in the systemthat is the basis of the MIaaS portal, for example, in IBM TivoliService Request Manager (TSRM) software available from InternationalBusiness Machines Corporation, Armonk, N.Y., USA). In step 1310, theprovisioning takes place and the imported instance is picked up and anynew adjustment sub-flows are called (can be carried out, for example, inTSAM). In step 1312, a virtual server is created. (This is not needed ifthe instance remains the same, i.e., if the landing zone is purelyvirtual as described above.) (This can be carried out by the normalinstance creation internal to the MIaaS cloud, for example, in TSAM). Instep 1314, carry out server validation of the MIaaS cloud (assuming theMIaaS cloud has that and does not entirely rely on the prior steps tosucceed without test); preferably with no changes, but more problems maybe expected to be identified at this point for migrated instances thanfor instances provisioned from catalog images, and thus more time forremediation may be reserved.

In step 1316, prepare the instance for customer test access by providingappropriate keys to the customer. In step 1318, fulfillment of therequest (i.e., the initial input to this flow) is validated if needed;this can be done via a shortened and automated process in one or moreembodiments, where this is just a sub-flow in a larger migration flow,compared with the normal situation where this was a customer request tothe MIaaS cloud portal.

The depicted sub-flow corresponds to step 556.

Backup/snapshots and tests (the neighboring overall steps) may occurbetween any of these sub-flows; even inside them, in particular in theprovisioning flow 1310 after individual adjustments.

Start Adoption Flow with Instance Parameters 1304

In a non-limiting example, the portal is implemented in TSRM andincludes a graphical user interface (GUI) and REST API (applicationprogram interface). In one or more embodiments, starting via REST API isbelieved to be appropriate as all parameters should be clear from theresults of the analysis and plan step 524. Those may reside in adatabase or another well-defined repository so that they can beretrieved by software. While in FIG. 5, the analysis and planningcomponent is depicted in the customer environment 402, where thediscovered data arise, at some point the relevant part of the data forthe adjustments step 556 should be transported to the MIaaS cloudenvironment 410, in particular its Cloud Management zone 680 (this arrowwas omitted in FIG. 5 to avoid clutter). The transfer agent 682 andtransfer core component 690 can take this on as an additional taskbesides transporting images. However, in some cases, it may be desirableto initially start via a GUI in order to more easily track theactivities.

In one or more embodiments, the results of the analysis and plan step524 relevant for this sub-step should include the instance data, zoningplans, and the like so that the correct parameters can easily be inputto the REST API or entered by a human operator into the GUI.

A naming/location scheme should be provided for instances in the landingzone so that at this point, information regarding which instance is tobe registered can be input. In one or more embodiments, this is the nameunder which VMware vCenter Server knows the instance in question. In oneor more embodiments, an automated check of the GUI inputs (size, OS)with the actual values of the instance is useful.

FIG. 14 shows an exemplary “Create Server” pop-up 1404 from an MIaaSportal GUI Portal Design self service center 1402. Migration servers aregrouped into a project, and if each migration request can contain morethan one instance (called image in this GUI), a “Configuration Set”option is provided. The user is given the option to fill in the name ofthe image he or she wants to use, or to click a magnifying glass to seea list of available images. VM size info should be part of the metadatafor the image in one or more embodiments, possibly with an option tochange same. The “migrate server” button starts the actual registrationflow. The portal may now perform certain activities, such as recordingthe started flow in storage, and allowing its status to be queried fromthe GUI or the REST API.

Portal Flow—Passes “Adoption” Parameters Through 1308

Typically, the portal is a separate software component 1110 (inparticular, part of the BSS) from the provisioning engine 1112, thecomponent that carries out the actual registration (often a workflowengine, and part of the OSS), Hence the portal transfers theregistration request to the provisioning engine. Compared with thenormal provisioning request transferred between these two components,the choice of “registration” or “import” of a migrated instance, and thelocation/name of the instance is passed through, i.e., those are newparameters in that request in that API.

Provisioning Flow—Instance Pickup Step 1310

In one or more embodiments, based on a suitable naming/location schemein the landing zone, and the provisioning engine 1112 (e.g., TSAM)obtaining the name/location of the instance to adopt from the portal1110 (e.g., TSRM), the pickup is clear. In a non-limiting example, thename of the instance in an underlying VMware vCenter server may be used.This name might not be globally unique, but should be acceptable if thehostnames are used, which can otherwise be assumed to be all differentalready.

In embodiments where the landing zone is physically separated, certainfirewall settings and a copying process to implement the actual pickupmay be employed (which are a bit different from taking an image from theMIaaS image library).

Provisioning Flow—Adjustment Overview 1310

Turning now to FIG. 15, at 1502, note the customer instance aftermigration but before adjustment, i.e., the instance on a cloudhypervisor 554 in the landing zone directly after transport 538, and at1504, the customer system after migration and adjustment (broken downinto customer portion 1506 and cloud service provider portion 1508),i.e., as it will be in the production zone at 558. With regard toapplication/middleware layer 1510, little or no change is typicallyplanned at this level (in particular because migration only to an MIaaScloud, not a PaaS cloud, is considered in this example), except someconfiguration changes due to potential change of some basic OSconfiguration aspects such as IP address. In one or more embodiments,applications are not touched in this flow, inasmuch as P2V typicallyworks well and this flow can be implemented with standard P2Vtechniques. With regard to application/middleware management layer 1512,little or no change is typically planned at this level, except someconfiguration changes in terms of security and due to potential changeof some basic OS configuration aspects such as IP address.

With regard to OS management layer 1514, this flow includes removal ofcustomer management suite components that are no longer required andpolicy adjustment of those that are; and installation of a standardmanagement suite of the cloud services provider as well as a cloudmanagement tool of the cloud services provider (with regard to thelatter, in at least some cases, agents are implemented in the previousaspect, and central tools are already present). In some cases,installation is implemented via a standard provisioning flow. Removaland policy adjustment are significant tasks.

It should be noted with regard to aspects 1512, 1514, that some toolsmay be common for the OS and App/MW layers.

With regard to OS layer 1516, in one or more embodiments, a minimum setof OS patches are installed as required by the cloud services providerto accept the Base OS (in an alternative embodiment, this can beimplemented as a separate flow within otherwise BAU cloud management).In some cases, an “open ports” check is carried out. In one or moreembodiments, no change is needed at the base operating system levelexcept for required OS configuration updates such as IP address.

Options to Handle Agents

In one or more embodiments, significant options, to be decided per agenttype, include:

-   -   Can certain agents be ignored? (Easiest flow)    -   Must some agents be retained? In a non-limiting example, there        may be a definite sentiment to keep AD (Active Directory        authentication product available from Microsoft Corporation,        Redmond, Wash., USA) and Altiris (for applications). In one or        more embodiments, everything that is used for application        management should stay, possibly with changes.    -   Should some agents be deactivated? This means shutting them        down, but not uninstalling them. This is an option where agents        no longer seem needed, but from the given information this is        not quite clear yet and thus uninstalling is risky.    -   Can/must some agents be completely uninstalled? In some cases,        this may be appropriate to tidy images up, or because the agents        need resources (e.g., NetIQ needs significant CPU for its        monitoring). In one or more embodiments, complete        un-installation is never mandatory, as the customer can have all        sorts of things on these servers and the cloud service provider        does not judge that.    -   Agents are typically not allowed to have root/admin rights. At        this point, it should be determined whether those that must be        retained will run without root/admin rights; and what more        explicit rights do they may need. An example is Altiris to only        patch applications.

In some embodiments, the cloud services provider may inquire of thecustomer as to how the customer employs these tools, what policies thecustomer has, where the tools are installed, and so on.

It should also be noted that any changes planned by the cloud servicesprovider may need a significant new discovery effort—at least if thecustomer's installs are as variable as those of other software, and aslittle standardized.

Minor Version, Fixpack, and Security Patch Updates

It is worth noting that the BigFix tool, now known as IBM TivoliEndpoint Manager, available from International Business MachinesCorporation, Armonk, N.Y., USA, is believed to be one particularlyuseful tool for security patches; however, other embodiments may useother tools.

Change of Addresses in Other Components

In a non-limiting example, the following address choices are made:

-   -   The images retain their DNS names, i.e., during cut-over the        customer will change the DNS entries for their domains. (This is        much easier than changing the DNS names, which may be used        inside many components of the application/middleware layer 1510        and its management 1512.)    -   The instances get two new IP addresses, on new virtual NICs        (network interface controllers), to enable management and backup        tasks of the MIaaS cloud without interfering with the normal        traffic over customer IP addresses and (virtual) NICs.    -   The IP addresses from the customer environment are replaced by        addresses in a subnet of the MIaaS cloud production zone; this        is what should be entered in the above DNS entries.

Hence, in one or more embodiments, there is no need to change otherservers or clients addressing the migrated instances, assuming the otherservers or clients use DNS names (rather than using IP addressesdirectly); this has become increasingly common.

In some cases, where it is desired to reduce costs, the migration teamcannot readily determine whether the customer used IP addresses foraddressing. In such cases, it may be appropriate to assign to thecustomer a requirement to ensure that such is not the case. If thisrequirement is violated, problems may occur in user acceptance testing560, and remediation will return the instances or entire workloads tothe customer. This problem is independent of the migration path ortarget, in particular of the fact that migration is to an MIaaS cloud.

Create Virtual Server 1312

In one or more embodiments, if it is possible to just retain theinstance and at most put it into a different VLAN via virtual switch andfirewall changes, then it is not necessary to create any server at thispoint. Otherwise the virtual server creation works exactly as instandard provisioning of the MIaaS cloud.

Prepare Instance for Customer Test Access (Keys)

At this point in the adoption and adjustment flow, all significantthings that need to be done on the instance itself have been carriedout, and the customer is given access for testing the image as well.Most customer IDs should, at this stage, still be on the instance or therespective active directory (AD). Those that changed due to rightsreduction of agents should typically be set already. In some cases, thecloud services provider may need to hand out keys if access to the imageis key-based. In one or more embodiments, this works the same as in theprovisioning flow for catalog images described elsewhere herein.

Server Validation 1104

The validation as such can be unchanged from the provisioning flow forcatalog images. In one or more embodiments, failure at this point isbelieved to be significantly more likely in the case of a customerinstance than in the case of a cloud services provider catalog image. Inat least some cases, the cloud services provider may provide appropriateremediation.

It will be preferable to automate as much as possible of this validationand also of appropriate remediation if tests fail. Even better, however,wherever automated tests and remediation can be done at all, it may beadvisable to undertake such aspects in the already in the adjustmentstep, even if they are repeated again in the server validation phase forcompliance or audit reasons.

Request Validation 1105

In the migration scenario, where it is known in advance what will happenon each weekend (or other period of time), this aspect is preferablykept short and largely automated. The final approval from the customerafter UAT may still need manual entry though.

At this point, the overall rapid migration flow from FIG. 5 can beresumed, after the details of adoption and adjustment (Step 556 and thesubsequent transfer of the instance into the production zone, as shownin 558). Now the user acceptance test (UAT) 560 takes place (typicallynot only of one instance but of a business application supported by thisinstance and possibly others). If it fails, a manual decision should betaken, together with the customer, bearing in mind the followingaspects:

-   -   the issues may be minor ones that can be fixed locally in the        cloud production zone 574 (e.g., DNS or firewalls not brought up        correctly)    -   it may be known that an adjustment failure is the issue—the        particular adjustment may be skipped, e.g., a particular        security patch. If the individual operation (such as an attempt        to install a security patch) doesn't come with a safe roll-back,        the cloud services provider can roll back to the previous stored        instance. If there was a manual decision in this adjustment, the        cloud services provider can, in some cases, try again with a        different decision.    -   In some cases, if it is not known that the issue is an        adjustment failure, or issues cannot be repaired within the        change window, or the variance goes beyond a certain threshold        (e.g., more than five (for example) security patches can't be        applied) then cancel the migration of this instance (and        possibly of the entire business application). Restart the        customer instances 520 or 522, typically based on the backup        532.        Cut-Over and Taking New Instances into Use (564)

If the UAT is passed, the instances of one business application or othermigration unit in the cloud begin to be used by the customer. In theaddressing choices are made as in the example above, the DNS of thecustomer is changed at this point; this can include changing reverse DNSentries—possibly as part of a standard procedure. In some cases, thechange window can end here. If the customer had specific warnings, suchas “application down” on a web entry page, they can now be taken offAppropriate customer training can be provided if desired.

It is worth repeating that one or more embodiments offer the advantagesof traceability and/or roll-back capability. Furthermore in this regard,traceability is a significant advantage and it is quite helpful formanaged environments to have every step and especially adjustments doneto the image clearly documented. The adjustment engine as well asTSAM/TSRM have the ability to create instance-specific logs forfully-transparent/change-controlled migrations. With regard to roll-backcapability, the adjustment engine operates in a step-by-step mode andoffers the ability to roll-back a certain adjustment if something wentwrong. That ability together with the snapshots creates a relativelysafe environment to execute the needed migration/adjustment steps.

Recapitulation

Given the discussion thus far, it will be appreciated that, in generalterms, an exemplary method, according to an aspect of the invention,includes the step 404 of transferring a foreign instance 684 from acustomer environment 402 to a target infrastructure-as-a-service cloudenvironment 410 as an image. This step can be carried out, for example,via component 690, optionally by interfacing with agent 682. A furtherstep 406 includes adjusting the foreign instance to standards of theinfrastructure-as-a-service cloud environment to obtain an adjustedinstance. This step can be carried out, for example, via component 692.A still further step 408 includes registering the adjusted instance intoa management system (generally 410; specifically 696, 698 in one or moreembodiments) of the infrastructure-as-a-service cloud environment.

In general, the adjusting may include adjusting the foreign instancewhile it is running, or alternatively, adjusting the foreign instance asthe aforementioned image.

In some cases, the registering includes running at least a portion of aprovisioning flow (e.g., as shown in FIG. 11) for a standard catalogimage of the infrastructure-as-a-service cloud environment (the standardcatalog image is selected for similarity to the foreign image); andswapping the image of the foreign instance for the standard catalogimage. In general, such swapping may be carried out during theprovisioning flow or after the provisioning flow; when carried outduring the provisioning flow, it is referred to as picking up the imageof the foreign instance, during the provisioning flow, rather thanswapping. Furthermore, swapping “after the provisioning flow” should beunderstood to include being after step 1102 (and optionally after mostor all of step 1103, but before 1104).

Furthermore in this regard, consider three ways to proceed. Recall thatprovisioning flow for catalog images is shown in FIG. 11. In some cases,proceed through the provisioning flow almost to the end like steps1101-1103 to obtain a provisioned instance; then discard thatprovisioned instance and replace it with what is being migrated. (Thisis referred to as “swapping”) In some embodiments, the catalog image isnever really put on the server. At the point where the catalog imagewould be copied, pick up the instance and let the rest of theprovisioning flow work on the migrated instance so there is less work todo at the end (FIG. 13 step 1310). In one or more embodiments, thispoint is in the sub-step “create virtual server” of step 1102. Suchcreation is detailed in step 1103. Within the virtual server creation,this point is in the sub-step “copy the image over”—in this aspect, theimage of the imported instance instead of the catalog image is what iscopied.

As noted, in one or more embodiments, the infrastructure-as-a-servicecloud environment is a managed-infrastructure-as-a-service cloudenvironment. Thus, in such cases, the transferring includes transferringto the managed-infrastructure-as-a-service cloud environment; theadjusting includes adjusting to standards of themanaged-infrastructure-as-a-service cloud environment; and theregistering into the management system includes registering into amanagement system of the managed-infrastructure-as-a-service cloudenvironment.

As noted elsewhere, in the adjusting step, in some cases, the standardsinclude one or more of security standards; infrastructure standards;patch managements standards; and infrastructure management systemstandards (e.g., standards of tools such as 696, 698).

In some cases, an additional step 524 includes analyzing the foreigninstance for suitability for transfer to the targetinfrastructure-as-a-service cloud environment; in such cases, thetransferring is responsive to the analyzing yielding an affirmativeresult.

As noted, in some cases, a plurality of foreign instances are treated asa whole in the analyzing step.

In some cases, an additional step includes carrying out testing (refer,e.g., to decision blocks 404, 406, 408; in general, such testing can becarried out, for example, before the transport, after the transport,between different adjustments, after adjustments, and after migration. Afurther step includes carrying out at least one of remediation andback-out if the testing fails (“Not OK” branches of blocks 404, 406,408). As noted elsewhere, in some cases, a plurality of foreigninstances are treated as a whole in the testing step.

In some cases, the testing includes a baseline test 528 prior to thetransferring step; and a user-acceptance test 560 after the registeringstep. The user acceptance test has at least one test case. The baselinetest validates that the foreign instance initially passed the at leastone test case of the user-acceptance test.

In another aspect, an apparatus includes a memory (e.g., RAM 30, cache32); and at least one processor 16, coupled to the memory, and operativecarry out or otherwise facilitate any one, some, or all of theaforementioned method steps. Optionally, the apparatus further includesa plurality of distinct software modules 42. Each of the distinctsoftware modules is embodied on a computer-readable storage medium, andthe distinct software modules include a transfer core component module,an adjustment component module, and a registration component module; asdiscussed elsewhere herein. The snapshot management system moduleoptionally includes one, some, or all of the sub-components in FIG. 10.

In some cases, the transfer core component module obtains the foreigninstance from a transfer agent in a customer environment and locates theforeign instance within a cloud landing zone of theinfrastructure-as-a-service cloud environment. In some embodiments, theat least one processor is operative to instantiate the adjusted instanceinto a cloud production zone of the infrastructure-as-a-service cloudenvironment.

In another aspect, in some cases, the infrastructure-as-a-service cloudenvironment includes a cloud landing zone, a cloud production zone, anda cloud management zone. In at least some such cases, the at least oneprocessor is operative to transfer the foreign instance into the cloudlanding zone under control of the cloud management zone; the at leastone processor is operative to carry out the adjusting on the foreigninstance in the cloud landing zone under control of the cloud managementzone; the at least one processor is further operative to instantiate theadjusted instance into the cloud production zone; and the managementsystem forms at least a portion of the cloud management zone.

In some cases, the cloud production zone includes cloud production zonecomputer hardware of a first type and cloud production zone hypervisorsof a first type running on said cloud production zone computer hardwareof said first type; and the cloud landing zone includes cloud landingzone computer hardware of the first type and cloud landing zonehypervisors of the first type running on the cloud landing zone computerhardware of said first type. Fewer standards are imposed on instancesmanaged within said cloud landing zone than on instances managed withinsaid cloud production zone, and said cloud landing zone is separatedfrom said cloud production zone via at least one of physical and logicaltechniques so as to avoid impact of said cloud landing zone on securityof said cloud production zone. Stated in another way, the cloud landingzone is a set of computer hardware (e.g., servers, storage devices,etc.) and hypervisors of the same type as in the cloud production zone,but with fewer standards on the instances managed there, and physicallyand/or logically separated from the cloud production zone so as not toimpact the security of the cloud production zone.

Management Infrastructure Analysis for Cloud Migration

One or more embodiments advantageously provide techniques for managementinfrastructure analysis for cloud migration. In current migrationanalysis techniques, in particular the automated parts thereof, thefocus is on key middleware such as application servers or databases. Onesignificant advantage of the cloud computing paradigm lies in simplifiedmanagement, which mainly comes from standardized infrastructure softwareand standardized management processes. One or more embodimentsadvantageously extend automated migration analysis to these managementaspects.

In an Infrastructure as a Service (IaaS) cloud, the capability providedto the consumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls). AHardware-Infrastructure-as-a-Service (HIaaS) cloud provides bare-bonesvirtual machines as a service. It may also provide an operating system(OS) and even software, but no support is typically provided for the OSor software.

On the other hand, a Managed-Infrastructure-as-a-Service (MIaaS) cloudprovides full-service virtual machines. The service may, e.g., includeOS patching and support for security and compliance of the OS. Onesignificant aspect of MIaaS is simpler management via: standardizationto a certain set of catalog images from which instances are generated,automatic linkage of these instances to management tools duringdeployment, and/or not giving customers administration privileges on theOS level, so that the operating systems on the instances remain as thecloud administrators configure them.

Heretofore (prior to the emergence of the cloud computing paradigm),there was much less need to analyze for compatibility withinfrastructure standards, or for the costs associated withtransformation thereto. One aspect of the cloud computing paradigminvolves enhanced efficiency through the standardization ofinfrastructure. The move to cloud computing also reflects a trendwherein information technology (IT) running costs have outpaced ITinvestment costs. To gain large benefits from investments in cloudcomputing resources, one or more embodiments advantageously facilitatemigration of existing environments to such standardized infrastructuremanagement systems and processes, starting with analysis.

Reference is made to the definitions of IaaS clouds, HIaaS cloud, MIaaSClouds, Instance, Source instance, Image, Catalog image, Provisioning,Reinstall migration, Image-based migration, and Rapid migration to MIaaScloud as defined elsewhere herein.

Refer now to FIG. 16, and note cloud description 16300; discovery andanalysis of a source system to be migrated, shown at 16100 (an exemplarysource system per se is shown in FIG. 17); and an infrastructurecomparison engine 16200 to carry out comparison (referred to also asanalyzing, mapping, and/or matching) between the two. Cloud description16300 includes cloud infrastructure software standards and/orconfigurations (“configs”) 16310, 16320. Also included therein is anapplication-level description of cloud infrastructure management 16330;for example, a service-level agreement (SLA) offered by a cloud, ornon-functional requirements that can be set as part of an applicationprogram interface (API). Optionally, description 16300 also includesinclude cloud infrastructure management processes 16340.

With regard to discovery and analysis 16100 on the source system to bemigrated, step 16110 includes discovery of source infrastructure clientsand servers; step 16120 includes discovery of source infrastructureconfigs and/or logs; and step 16130 includes obtaining (for example, byderivation) of an application-level description of the sourceinfrastructure management. Optionally, process 16100 also includes step16140, namely, discovery and/or learning with regard to infrastructuremanagement processes of the source.

Process 16200 includes a comparison between the source and the targetcloud. Step 16210 includes a matching between the source and cloudsoftware, optionally taking transformation costs into account, and basedon the cloud infrastructure software standards 16310 and the discoveredsource infrastructure clients and/or servers from step 16110. In one ormore embodiments this matching process involves looking for conflicts asdescribed elsewhere herein:

-   -   a source infrastructure management component manages at least        one object that at least one mandatory target infrastructure        management component will manage in the target cloud        infrastructure    -   a source infrastructure management component uses at least one        resource that at least one mandatory target infrastructure        management component will use in the target cloud infrastructure    -   current lack of a mandatory target infrastructure component on a        client    -   existence of a mandatory target infrastructure component in a        different version    -   existence of a mandatory target infrastructure component with        different configurations.

In step 16220, map the infrastructure configurations based on the cloudinfrastructure config standards 16320 and the discovered sourceinfrastructure configs and/or logs from step 16120. In step 16230, mapthe application-level descriptions (e.g., descriptions of non-functionalrequirements as discussed elsewhere herein) of infrastructure managementfrom the cloud (from 16330) and the source (from 16130). In optionalstep 16240, map the infrastructure management processes from the cloud(from 16340) and the source (from 16140).

Again, comparison and/or analysis 16200 steps can involve, in one ormore embodiments, examining for conflicts.

With reference to steps 16340, 16140, and 16240, comparing the actualmanagement processes is optional. In particular, if a radical migrationsuch as to an existing cloud is made, then typically only theapplication-level descriptions need to be mapped. With regard to step16120, in one or more embodiments, infrastructure configurations arediscovered for mapping to potentially different software in the targetcloud (purely by way of a non-limiting example, HP event filtersassociated with products from Hewlett-Packard Company, Palo Alto,Calif., USA might be used in the source environment and might be mappedto IBM Tivoli Monitoring (ITM) event filters, available fromInternational Business Machines Corporation, Armonk, N.Y., USA, whichmight be used in the target environment). With regard to step 16130,several source aspects that are usually obtained by human interviews canbe derived from the detailed discovery, such as high-availabilityconfigurations, planned downtimes, and patch management setups. Even ifstill obtained by human interviews, they can be considered in automatedanalysis in step 16230 if the results are in a fixed format. With regardto step 16230, the application-level description of the currentinfrastructure typically has to be reached or exceeded, unless thebusiness owners explicitly agree to a lower level.

In an alternative approach, instead of having a cloud descriptionalready given, derivation of the most suitable cloud description for thesource environment may be part of the engagement, e.g., when the overallgoal is to build a suitable private cloud for an enterprise.

By way of review and provision of additional detail, before performingany IT migration, transformation, modernization etc., it is advisable toanalyze compatibility between components to be retained and newcomponents to be used. This may include, for example, selection of whatto retain and what to change, as well as effort analysis of changes tobe made to achieve compatibility.

Current migration analytics, in particular the parts done withwell-defined methods or even in an automated way, focus on compatibilityon the operating system level, and sometimes on compatibility of keymiddleware such as application servers or databases. That is to say,they analyze whether an operating system version will still run on newhardware, or whether a database version will still run on a newer orrelated operating system version.

With the advent of clouds, in particularManaged-Infrastructure-as-a-Service (MIaaS) clouds, current migrationanalytics are insufficient, as these clouds also prescribeinfrastructure management tooling and processes, as well as certainstandards on servers that allow the infrastructure management to operatein a standard way.

One or more embodiments advantageously provide a system and method forautomated migration analysis for infrastructure management aspects,primarily for cloud migrations.

One or more embodiments advantageously provide a systematic and/orautomated method for infrastructure management analysis.

Analyzing for infrastructure management migration is different fromanalyzing for middleware compatibility, because a significant questionis whether the source infrastructure management software conflicts withthe standard infrastructure management software in the cloud (inparticular MIaaS) and needs to be removed or modified (as opposed towhether the source infrastructure management software will run on thecloud operating system(s), which is what would be analyzed if theanalysis were for middleware compatibility). Furthermore, other settingsrelated to infrastructure management standards need to be analyzed, suchas assumed minimum patch levels.

In MIaaS cloud, migration implies the need for infrastructure analysis.One or more embodiments advantageously provide the ability tosystematically analyze infrastructure changes needed and to apply themin a “rapid migration” process as described elsewhere herein.

Referring now to FIG. 19, in some instances, an exemplary method isimplemented in two phases. In a first phase 1902, the to-be-analyzedelements, in particular the source infrastructure clients and serversfrom all source systems may be aggregated and discussed with thecustomer (i.e., the owner of or party responsible for the sourcesystem). For example, a cloud services provider may indicate to acustomer that it is necessary to uninstall all of the customer's“Vendor-X-patching systems.” In a second phase 1904, the decisions areapplied to individual source systems, and possibly refined if no generaldecision was possible in the first phase.

In one or more embodiments, it is believed advisable to detect conflictspertaining to conflicting management in the first phase. Unless acomprehensive list of all potential infrastructure software is available(this would be the case if Phase 0, numbered 1901, could already fill inthe database 1908 very well, and all software in the customer's sourceenvironment were already in such database), it is appropriate to analyzethe overall software list at this time to see if there are suchconflicts. Over time, the aforementioned database 1908 of conflictingand non-conflicting software can be developed.

In some instances, the discovery of source infrastructure software 16110can be done by carrying out discovery on the actual machines to bemigrated, which contain clients of this source infrastructure software(e.g., asset management agents); by detecting servers of this sourceinfrastructure software (e.g., a central asset management server);and/or from questionnaires of deployed infrastructure tooling.

Thus, one or more embodiments advantageously provide a method formanagement infrastructure analysis for cloud migration includingdiscovering infrastructure components in the source infrastructure; andanalyzing the discovered infrastructure components for conflicts withmandatory infrastructure components in the target infrastructure.

In some cases, the infrastructure components include one or more ofinfrastructure clients, infrastructure servers, infrastructureconfigurations, and infrastructure processes.

In some embodiments, conflicts include those where a sourceinfrastructure component manages the same objects that a mandatorytarget infrastructure component will manage.

In some cases, conflicts include those where a source infrastructurecomponent uses the same resources, in particular a port, as a mandatorytarget infrastructure component uses.

Non-limiting examples of conflicts include one or more of the currentlack of a mandatory target infrastructure component on a client, theexistence of a mandatory target infrastructure component in a differentversion, and existence of a mandatory target infrastructure componentwith possibly different configurations.

In some embodiments, the result of the analyzing step includes one ormore of the recommendations to uninstall an infrastructure component, toinstall an infrastructure component, to modify the configuration of aninfrastructure component, to exclude servers with a particular componentfrom migration, or to further discuss with the customer about aninfrastructure component. Furthermore in this regard, the last twooutcomes may occur in particular if a source infrastructure component isin a conflict, but likely to also be used to manage objects that are notunder control of the cloud, e.g., middleware in a migration to an MIaaScloud.

In some cases, the analyzing step is done in two phases; a firstaggregated phase where all discovered infrastructure components areaggregated and generic recommendations given for them, and a secondper-instance phase where the recommendations are applied to individualsource systems, and refined if the general recommendation was notconclusive.

The analyzing step can, in at least some embodiments, includeconfiguration comparison and/or process comparison.

With regard to configuration comparison step 16220, in some cases, it isadvisable to compare configurations and make decisions for changes. Thisis particularly advisable if infrastructure software is used to manageboth operating system (OS) aspects and application aspects. Forinstance, patching software on a source server may be set up to patchthe OS as well as databases and web servers. If this source server ismigrated to an MIaaS cloud, then the OS-level patching needs to beswitched off in favor of the cloud patching software, while the databaseand web server patching needs to remain. On the other hand, in othercases, the source software may be uninstalled, but the server owners maywish to retain certain policies, e.g., backup frequencies or types ofmonitored events.

Consider now aspects of customer dashboards 1707 as shown in FIGS. 17and 18. A related alignment question that can occur with MIaaS migrationis integration into overall customer dashboards. For example, thecustomer may have a “CIO (chief information officer) dashboard” thatgives an overview of the status of applications and servers. Thecustomer may desire to retain such a dashboard after migrating someservers to MIaaS, both because the dashboard also shows applications,and/or because not all servers were migrated, but the customer wouldlike a joint overview over migrated and non-migrated servers. In thesecases, adapters from the reporting features of the MIaaS software intothe customer dashboard should be provided. This aspect is shown in FIG.18 by linking dashboard 1707 also to the target management program 2,numbered 1806, which is provided by the cloud.

Pertinent observations will now be provided regarding OS versions,patches and security. Another infrastructure aspect that an MIaaS cloudwill typically prescribe are precise OS versions. For the OS, it istypically appropriate to decide what level of deviation is tolerated,and what may be automatically updated prior to migration. For example,it might be decided to tolerate deviating minor versions (e.g., v5.2instead of 5.3) or not, and there are often automatic updates toolsamong minor versions. It is also appropriate to consider non-version OStypes, such as releases or editions.

Patches may need to be added in some cases. However, if source serverswith back-level patching are found, it is not unlikely that there wereapplication problems with some newer patches. Ideally, an effort shouldbe made to try to find this out from the application owners beforehand.Patch updates should typically be followed by careful application tests.

With regard to other security settings, there are a number of goodpractices for security such as not enabling certain services and accessrights to certain OS files. The source server should be brought intocompliance with such requirements. Ideally, existing deviations fromsuch best practices are not required by applications (e.g., applicationsshould not require that an operating system administration password isonly 6 characters long), but this should be discussed with applicationowners beforehand too.

In one or more embodiments, there are at least two significant ways ofdeciding what to change regarding operating system settings and thelike, and in particular security-related settings:

-   -   Compare with clean cloud images from a catalog. In some        instances, this approach may be problematic, inasmuch as        application-level and OS-level settings are not cleanly        separated on typical operating systems. For example, if a source        image has a service at a port where the catalog image does not,        it is typically necessary to validate whether that is a useful        application service.    -   Compare with a security validation mechanism if the cloud has        such a mechanism, e.g., a service activation check. Settings        validated here typically must be achieved. However, such a test        in a cloud might be incomplete because the cloud might rely on        the cleanness of its catalog images.

Thus, in some cases, there can be a general cloud migration analysisphase before both of the above-mentioned phases, wherein decisions aretaken as to which security settings are mandatory. Phase 0 in FIG. 19,numbered 1901, depicts a general cloud migration analysis for managementsoftware; a similar scheme as depicted therein can also be used to carryout a general cloud migration analysis for OS settings.

Continued reference should be had to FIG. 16, and reference should alsonow be had to FIG. 17. FIG. 17 shows an exemplary source environment1702 on which discovery and analysis could be carried out. Environment1702 includes a server 1703 with a management program 1, numbered 1701.Environment 1702 also includes a server 1704 with a management program1706 interfacing with logs and/or configurations in a data store 1708.Physically, data store 1708 may or may not reside on the same virtual orphysical server as the management program 1706. That is to say, theconfigurations 1708 could also be inside server 1704; however, with alarge management program, it is indeed possible that a configurationdatabase 1708 is elsewhere (i.e., outside server 1704).

Two management programs are shown in FIG. 17 for brevity; in a typicalscenario, long lists will be present. The management programs 1701, 1706could correspond, for example, to “backup management” and “compliancemanagement.”

Environment 1702 also includes (in this example) two instances 1709,1716. These are instances similar to those migrated in the rapidmigration approach discussed elsewhere herein, i.e., they can bephysical or virtual. The servers 1703, 1704 can in principle be virtualtoo, and a few of them might be migrated, so in one view they are alsoinstances. One or more embodiments, however, address the case whereinthe cloud has its own management programs (in the cloud management zone1899 of FIG. 18) so the servers 1703, 1704 are not migrated.

Environment 1702 includes one or more clients 1710, 1713, 1732 managedby management programs 1701, 1706. These clients may, for example,reside on instances 1709, 1716 and may be clients in the sense of howthey relate to management programs 1701, 1706, while instances 1709,1716 may also function as servers on which one or more applications1712, 1714, 1718, 1720 run. Instance 1709 is managed by both managementprograms 1701, 1706, while instance 1716 is managed only by managementprogram 1706. This demonstrates the desirability of per-instanceanalysis.

Instance 1709 has OS settings 1711 and instance 1716 has OS settings1717. Client 1710 has configuration file 1715; client 1713 hasconfiguration file 1731; and client 1732 has configuration file 1733.

In FIG. 18, which depicts an exemplary target (cloud) environment 1802,it is assumed that the management program 1, numbered 1701, was retained(and thus its server was migrated in the normal way into the cloudproduction zone—see instance 1803), while program 2 was exchanged for acorresponding program 1806 in the cloud (particularly, on server 1804,in the cloud management zone 1899). Program 1806 utilizes logs andconfigurations 1808, in a similar manner as program 1706 used logs andconfigurations 1708.

FIG. 18 also shows that OS settings changed somewhat (security, patch,or the like); this is illustrated by different numbers 1811, 1817 ascompared to settings 1711, 1717 in FIG. 17. Instance 1809 is the analogto instance 1709 in FIG. 17, i.e., the migrated version of instance1709; it includes unchanged client 1710 with config 1715 managed byretained management program 1, numbered 1701. It also includes client 2,numbered 1813, with config 1831, and managed by program 2 numbered 1806.Instance 1816 is the analog to instance 1716 in FIG. 17; it includesclient 2, numbered 1832, with config 1833, and managed by program 2numbered 1806. Applications 1712, 1714, 1718, 1720 now run in targetenvironment 1802.

In some cases, instead of retaining program 1, or as program 3, it isalso possible that the same management program already exists in thecloud management zone. Then the corresponding client can be retained,and the issue becomes whether the “config” also stays the same or ischanged to cloud standards for such “configs.”

FIG. 19 shows exemplary phases in management infrastructure analysis forcloud migration. There is essentially a preparatory Phase 0, numbered1901, followed by a two-phase analysis process including Phase 1,numbered 1902, and Phase 2, numbered 1904. In Phase 0, numbered 1901, at1905, based solely on cloud infrastructure standards, make abstractdecisions (for example, “no other OS patch management software mayrun”). At 1907, apply abstract decisions to some well-knowninfrastructure software packages. The result is (at least a partial)database 1908 of management clients (versions) and general decisions forthem; database 1908 can be updated later as explained below.

During Phase 1, numbered 1902, at 1911, discover source infrastructureclients and servers on each instance. In step 1912, aggregate thediscovered versions. In step 1913, make a general plan per managementclient version (part of matching step 210, but not per source instance).Step 1913 takes input from step 1905, step 1912, and database 1908, andalso updates database 1908 with its outputs. Step 1913 results in plan1914; it will be understood that plan 1914 is illustrative andnon-limiting.

During Phase 2, numbered 1904, per-instance decisions are made. Inoptional step 1916, if carrying out Phase 2 at a later time, re-discoverinfrastructure clients on the given instance (e.g., instance containsmanagement clients 1, 2, 5 mentioned in exemplary plan 1914). If nore-discovery is done, such knowledge is still available from step 1911.In step 1917, apply the plan to these instances. In the non-limitingexample, decide to uninstall client 1, retain client 2. Step 1917 thustakes input from optional step 1916 (else from Step 1911) and from plan1914. In step 1918, where plan 1914 indicated “needs per-instancedecision,” perform further analysis to decide (in the non-limitingexample, decide for client 5). In optional step 1919, proceed toinfrastructure configuration mapping (as in step 220). In the example,this is done, possibly, for clients 2 and 5.

FIG. 20 shows a possible user interface for a decision about a conflict,in particular for Phase 0 (Step 1907) or Phase 1 (Step 1913) where ageneral recommendation for a certain management software type is made.At 2002, a query is made whether the management software entered in thefield “Middleware name” conflicts with any software in the cloud SCE+,version 1.5. The response is shown at 2004: in this case, there isindeed a conflict, and an explanation of the type of conflict is given.In another usage, the port that a certain piece of software is runningon might be input (in the lowest input field in view 2002) to check forport conflicts.

The following code snippet in SQL is a simplified version of code thatcould be used for decisions in Phase 2 (Step 1917). Assume that software(management software and applications) installed on the source instancesis gathered in a table “MIDDLEWARE_INSTALL_MASTER”. Furthermore, assumethat component 1908 is realized as a database table“MW_MANAGEMENT_LOOKUP,” where it is assumed for simplicity thateverything with any conflict(s) is uninstalled, and precisely thesoftware with known conflict(s) is collected in this table. Theappropriate decision to make is whether to uninstall or not for each rowin the former table, based upon whether the middleware occurs in thesecond table. The following query does this, assuming the decision goesinto column “FUNCTION” of the former table:

update MIDDLEWARE_INSTALL_MASTER set FUNCTION = ‘UNINSTALL’ WHERE EXISTS(SELECT 1  FROM MW_MANAGEMENT_LOOKUP  WHEREUPPER(MIDDLEWARE_INSTALL_MASTER.MW_DISTRIBUTION_NAME) =UPPER(MW_MANAGEMENT_LOOKUP.AGENT_NAME) )

A possible result for a small subset of instances (given by column HOSTNAME) is shown in FIG. 21, by way of a non-limiting example.

Given the discussion thus far, it will be appreciated that, in generalterms, an exemplary method, according to an aspect of the invention,includes the step 16100 of discovering, in a source computing system1702 having a source management infrastructure, at least one sourceinfrastructure management component (examples given below). This stepcan be carried out, for example, using a suitable discovery tool, withappropriate modifications. In particular, known discovery tools coverinfrastructure software. However, where per-software modules are neededin the discovery software, the focus in existing packages may so far lieon middleware (databases, web servers, etc.) that new modules forinfrastructure software should be added. Furthermore, it may beappropriate to extend the reporting features of the tools to includeinfrastructure software, and for specific reports that characterizeinfrastructure software so that step 16110 has an output that makessteps 16210 and/or 16120 easy. Given the teachings herein, the skilledartisan will be enabled to make suitable changes to existing discoverytool packages to implement one or more embodiments.

A further step includes obtaining a description 16300 of a target cloudinfrastructure having a target management infrastructure (e.g. layer64). The description includes at least one mandatory targetinfrastructure management component. This step could be carried out, forexample, by using a suitable database program to query a description16300 stored in a database; non-limiting examples include IBM DB2software available from International Business Machines Corporation,Armonk, N.Y., USA, and ORACLE software available from OracleCorporation, Santa Clara, Calif., USA. It may also be done by querying acloud portal; if possible, via a programmatic interface, otherwise viaone or more user interfaces. If none of these options is available itcan be obtained manually from the cloud service provider. If that isalso not possible, a further option includes provisioning an image fromthe cloud catalog, and performing discovery on that image to see whatinfrastructure software is installed on same. This infrastructuresoftware is likely to be the cloud standard.

Thus far, it has been assumed that migration to a given cloud with givenstandards is desired. In some instances, there may still be a choicebetween multiple clouds; then multiple descriptions may be given andstep 16210 may additionally look for the best-matching cloud. In anotheraspect, the goal may be to build a private cloud for the given sourceenvironment; then, a suitable cloud infrastructure software standard maybe derived in step 16210 from analysis of the discovered sourceinfrastructure. For instance, if it is discovered that 80% of the sourceservers are monitored with monitoring software X, and 20% with othermonitoring products, then monitoring software X may be selected as thestandard for the new private cloud, and monitoring software changes willonly be needed on the remaining 20% of servers.

A still further step includes analyzing the at least one sourceinfrastructure management component to determine whether at least oneconflict exists with the at least one mandatory target infrastructuremanagement component. This step could be carried out, for example, usinginfrastructure comparison engine 16200; refer to description of block16210 elsewhere herein.

In the discovering step, the at least one source infrastructuremanagement component could include, for example, at least one sourceinfrastructure management client 1710, 1713, 1732; at least one sourceinfrastructure management server (1704 with program 1706) (clients andservers can be discovered in step 16110); at least one sourceinfrastructure management configuration (e.g., in data stores 1708,1715, 1731, and/or 1733); and/or at least one source infrastructuremanagement log (e.g., in data store 1708) (configurations and logs canbe discovered in step 16120). All the aforementioned elements thingswould typically be present, but they might not all be discovered. Forexample, the log might not be discovered. In at least some embodiments,when the focus is on install/uninstall, it is sufficient to discover theclient; and for the “Phase 1” analysis, it is sufficient to find themanagement programs.

In some cases, a further step 16130 includes obtaining a description ofnon-functional requirements of the source management infrastructure(e.g., with the aforementioned discovery tool) (also referred to hereinas an application-level description).

In some cases, in the obtaining step, the description of the targetcloud infrastructure includes cloud infrastructure software standards16310, cloud infrastructure software configurations 16320, and/or anapplication-level description 16330 of the target managementinfrastructure (i.e., a description of non-functional requirements onthe management infrastructure). These are typically given by theenterprise application supported by the currently considered instance.These can include, for example, an SLA or non-functional requirement,but SLAs can be seen as non-functional requirements as well. Otherexamples include change windows, up-to-dateness policies (such as forpatches or in monitoring for problems), auditing requirements, and thelike. Many of these would typically be input manually. It should beensured this is done in a fixed format to allow automatic comparison instep 16230. By way of a non-limiting example, if a cloud only providescertain patches every 4 weeks, but an enterprise application has acompliance requirement that requires such patches every week, then suchenterprise application cannot be run on this particular cloud.

In cases as mentioned in the preceding paragraph, the analyzing stepincludes matching the cloud infrastructure software standards with theat least one source infrastructure management client and the at leastone source infrastructure management server, as at 16210; mapping thedescription of the non-functional requirements of the source managementinfrastructure with the description of the non-functional requirementsof the target management infrastructure, as at 16230; and mapping thecloud infrastructure software configurations with the at least onesource infrastructure management configuration and the at least onesource infrastructure management log, as at 16220.

As indicated by the arrows from block 16210 to block 16220 and fromblock 16230 to block 16220, in some cases, the mapping, at 16220, of thecloud infrastructure software configurations with the at least onesource infrastructure management configuration and the at least onesource infrastructure management log is at least partially based on thematching, at 16210, of the cloud infrastructure software standards withthe at least one source infrastructure management client and the atleast one source infrastructure management server, and the mapping, at16230, of the description of the non-functional requirements of thesource management infrastructure with the description of thenon-functional requirements of the target management infrastructure.

In some embodiments, in the discovering step, the at least one sourceinfrastructure management component further includes at least one sourceinfrastructure management process, as shown at 16140; in the obtainingstep, the description of the target cloud infrastructure furtherincludes at least one target infrastructure management process 16340;and, as seen at 16240, the analyzing further includes mapping the atleast one source infrastructure management process with the at least onetarget infrastructure management process.

As indicated by the arrow from block 16230 to block 16240, in somecases, the mapping of the at least one source infrastructure managementprocess with the at least one target infrastructure management process,at 16240, is at least partially based on the mapping of the descriptionof the non-functional requirements of the source managementinfrastructure with the description of the non-functional requirementsof the target management infrastructure, at 16230.

In some cases, in the analyzing step, the at least one conflict includesthe at least one source infrastructure management component managing atleast one object that the at least one mandatory target infrastructuremanagement component will manage in the target cloud infrastructure.

In some embodiments, in the analyzing step, the at least one conflictincludes the at least one source infrastructure management componentusing at least one resource (e.g. port) that the at least one mandatorytarget infrastructure management component will use in the target cloudinfrastructure.

In some cases, in the analyzing step, the at least one conflict includesone or more of the current lack of a mandatory target infrastructurecomponent on a client, the existence of a mandatory targetinfrastructure component in a different version, and the existence of amandatory target infrastructure component with possibly differentconfigurations.

Consider the current lack of a mandatory target infrastructure componenton a client. For example, if the cloud requires event monitoring agent“ABC” in version 6.1 on all instances (i.e., ABC is a mandatorycomponent like 1813), and a source instance 1709 does not contain ABC inany version, a decision would be to install ABC. Consider the existenceof a mandatory target infrastructure component in a different version.For example, if source instance 1709 already contains ABC in version 4.5or 6.0, but the cloud requires 6.1, then it may be necessary to upgrade(probably easy if it was 6.0) or uninstall and reinstall (may be neededif it was 4.5, i.e., rather old).

Consider further the existence of a mandatory target infrastructurecomponent with possibly different configurations. If ABC in version 6.1was already there, or 6.0 was present and it has an upgrade feature to6.1, it may have a local configuration specifying what events itmonitors. On an instance provisioned from a cloud catalog image, adifferent configuration for ABC 6.1 may be present that monitors adifferent set of events. One solution is to overwrite the sourceconfiguration with the cloud standard configuration. Another is, in thisexample, to join the two configurations such that the union of the twosets of events gets monitored. This is possible if the correspondingcentral cloud management program, say “ABCServer” (corresponding to1706), tolerates when unexpected events come in. If ABCServer is theonly tool that processes these events, it may still be useless, but ifit forwards events to a customer dashboard 1707, it might pass theseunexpected events through. This could help if, e.g., the eventmonitoring system(s) was used both to monitor events from an application1712 (say crashes and restarts of this application) as well as OS-levelevents. The application 1712 remains under control of the customer andthe customer might still want to see these events in the dashboard 1707.

In some cases, the analyzing step includes one or more of (i)recommending un-installation of a source infrastructure component; (ii)recommending installation of a target infrastructure component; (iii)recommending modifying configuration of an infrastructure component;(iv) recommending excluding servers in the source environment with agiven source infrastructure component from migration; and/or (v) furtherdiscussing a given infrastructure component with a customer. The lasttwo outcomes (exclusions (iv)/further discussions (v)) may occur inparticular if a source infrastructure component is in a conflict, butthe same source infrastructure component is likely to be used to manageobjects that are not under control of the cloud, e.g., middleware in amigration to an MIaaS cloud (corresponding to application 1712, 1714etc.). With regard to possibilities (i)-(iii), the infrastructurecomponent(s) mentioned could be in the source environment prior tomigration, could be adjusted during rapid migration and/or aftertransport, and so on. With regard to possibility (iii), the same mightstart on either side—typically modification takes place if there wasboth a source configuration and a standard target configuration for thesame software, and some compromise is appropriate. With regard to (i),it could be decided that event monitoring software other than ABC is notdesired and any such software other than ABC could be uninstalled.

It is worth noting that “further discussion” option (v) may involvehuman agency. However, the automatic engine may need to output this as arecommendation. For example, if in 90% of the instances it can make anautomated decision, but in 10% of the cases it cannot, it is alreadywell worthwhile using such an engine. But the engine cannot simply guessin the remaining 10% cases, it must admit that it doesn't know. In someembodiments, these questions pop up in an interface with a structuredformat to answer them so that automation can proceed from there on. Ifseveral people need to decide a collaboration tool can be provided.

In some cases, the discovering includes discovering, in the sourcecomputing system, a plurality of source infrastructure managementcomponents; and the analyzing includes: initially aggregating all of theplurality of source infrastructure management components; developinggeneric recommendations for the aggregated plurality of sourceinfrastructure management components; applying the recommendations on aper-instance basis; and refining at least some of the appliedrecommendations in cases where the generic recommendations areinconclusive. See, e.g., FIG. 19 and accompanying text.

In some instances, the discovering is carried out on at least onephysical machine 1709, 1716 in the source computing system, and on thisat least one physical machine is software 1710; 1713 or 1732 that is aclient of the at least one source infrastructure management component.On the other hand, in some cases, the discovering is carried out on atleast one physical machine in the source computing system, and the atleast one physical machine is a server 1704 on which the at least onesource infrastructure management component runs. Questionnaires can alsobe used.

In some cases, an additional step includes providing a system, includingdistinct software modules; each of the distinct software modules isembodied on a non-transitory computer-readable storage medium. Thedistinct software modules include a discovery tool module to carry outdiscovery 16100, a description module to hold and access description16300 (see discussion above of obtaining description 16300), and aninfrastructure comparison engine module to implement engine 16200 andcarry out analysis. Examples of a description module include a suitabledatabase program to query a description 16300 stored in a database;cloud portal query code (querying, if possible, via a programmaticinterface, otherwise via one or more user interfaces); or code toprovision an image from the cloud catalog, and perform discovery on thatimage to see what infrastructure software is installed on same. Thisinfrastructure software is likely to be the cloud standard.

Non-limiting examples of discovery tools include IBM Tivoli ApplicationDependency Discovery Manager (TADDM) available from InternationalBusiness Machines Corporation, Armonk, N.Y., USA, the IBM Galapagostool, and the like. With regard to the IBM Galapagos tool, see, e.g.,Galapagos: model-driven discovery of end-to-end application-storagerelationships in distributed systems, IBM Journal of Research andDevelopment archive, Volume 52 Issue 4, July 2008, Pages 367-377. Insome instances, with respect to the discovery tool at least a portion(e.g., scripts or agents) typically runs in the source environment 1702,while another portion runs on a dedicated server in the targetenvironment. However, the entire discovery tool could run on a dedicatedserver in the target environment with a connection or connections to thesource environment 1702. In some instances, the entire discovery toolcould run on the environment 1702. Engine 16200 and the database withdescription 16300 would typically reside in the target environment(e.g., FIG. 3). They can also reside in a separate analysis environment,e.g., on servers of the team that performs the analysis. As discussedabove, existing tools can be modified to implement aspects of theinvention.

Use of Snapshots to Reduce Risk in Migration to a Standard VirtualizedEnvironment

A hardware infrastructure as a service cloud (HIaaS Cloud) provides barebone virtual machines as a service. It may also provide an operatingsystem and applications; however, support is typically not provided forany software installed on the virtual machine (VM). A non-limitingexample is the Amazon Elastic Compute Cloud (Amazon EC2) available fromAmazon Web Services LLC Seattle, Wash., USA. A managed infrastructure asa service cloud (MIaaS Cloud) provides full service virtual machines.The service contract includes providing software services for theunderlying virtual machine. These services include software upgrades,patch support, support for compliance, license management, and the likefor the provided software infrastructure. A non-limiting example is theIBM SmartCloud Enterprise+ also known as IBM SCE+, cloud environmentavailable from International Business Machines Corporation, Armonk,N.Y., USA. Image-based migration uses customer images for migration ofthe application to the cloud. This approach minimizes expensiveapplication re-installation. A cloud standard is the minimum set ofrequirements needed to be met by a customer image to be run and managedin cloud.

From an information technology (IT) management perspective, a hostingenvironment (a cloud is a non-limiting example) that aggressivelyenforces standardization (e.g., at operating system (OS), middleware,and/or application layer) can lead to significant management costsavings. However, migration of custom systems (called source systems)into such a standardized environment requires changes to be made to thesoftware stack of the source system in order to comply with thestandard. Those changes potentially carry a high risk of breaking thesource system, rendering it unusable.

In the recent years companies have increasingly adopted virtualizationto achieve hardware consolidation. One or more embodiments addressmigration into a standardized virtualized environment. One example ofsuch a standardized virtualized environment is an Infrastructure as aService (IaaS) Cloud. In one or more embodiments herein, a cloudenvironment is employed as a non-limiting example of a standardizedvirtualized environment. However, it is to be understood that one ormore embodiments are broadly applicable to a general standardizedvirtualized environment that may or may not expose the same kinds ofAPIs of an IaaS cloud.

One or more embodiments advantageously provide a system that reduces therisk of migration via the use of snapshots to systematically capturesystem states at critical points of time during migration. Moreover, oneor more instances provide a system that supports two types of snapshots:short term snapshots (STS) and long term snapshots (LTS), each optimizedfor specific usage scenarios. Furthermore, one or more embodimentsprovide a method that balances various requirements of “snapshotting”(resource utilization, performance impact, long-term preservation, andthe like) through a combination of short term snapshots and long termsnapshots. Even further, one or more instances provide a system thatsupports roll-back to any type of snapshot. Yet further, one or moreembodiments provide a system that automatically provides an audit of theexact changes applied to the source system through the migrationprocess. The changes can be viewed at two granularities: file level andproduct level. Two levels of information are available for a long termsnapshot: the file system (including meta-data information about eachfile such as file name, owner, permission, modified date, and optionallya hash of the content of the file); and the products (software packages)contained within the system.

For the avoidance of doubt, “snapshots” as used herein include bothlong-term snapshots and short-term snapshots; however, the process of“snapshotting” refers to the creation of a short-term snapshot while thecreation of a long-term snapshot is referred to as checking in or checkin.

The following is a non-limiting example of file-level and product-levelchanges referred to as “diffs”):

-   -   <removed-file name=“/Program Files/Altiris/Altiris        Agent/Software Delivery/pkgdlvlk.tmp”        digest=“sha1:da39a3ee5e6b4b0d3255bfef95601890afd80709”/>    -   <added-file name=“/cygwin/usr/share/groff/1.19.2/tmac/mm/locale”        digest=“sha1:da39a3ee5e6b4b0d3255bfef95601890afd80709”/>    -   <added-file name=“/IBM/ITM/InstallITM/MiaError.log”        digest=“sha1:da39a3ee5e6b4b0d3255bfef95601890afd80709”/>    -   <modified-file name=“/Documents and        Settings/Administrator/NTUSER.DAT”        old-digest=“sha1:33aca147bd43c253fbf904fea76aa63c1aab3b32”        new-digest=“sha1:7a12613062e36b27a4c20147ebd702671e0272ca”/>    -   <added-product vendor=“IBM” name=“IBM ITCAM for Microsoft        Applications Entry” version=“6.2”/>

Advantageously, one or more embodiments reduce the risk of migration byproviding a “time capsule” of the system being migrated, at criticalpoints of time during migration, such that the system can be rolled backto a “known good state” in case of failures. A customer will also knowwhat changes have been applied to its system during migration before thesystem is on-boarded into the cloud. The reduced risk translates toimproved engagement success rate, reduced downtime of applications, andlower migration cost due to reduced debugging time during failures.

It is worth noting that virtual machine (VM) snapshot and roll back is ageneral mechanism available in modern hypervisors, which have been usedin various scenarios, such as system debugging and/or system security.In one or more embodiments, the “short term snapshot” is essentially thesame as a VM snapshot; however, the usage scenario is different(reducing risk in migration). Additionally, one or more embodimentsemploy novel long term snapshots and the novel combination of the twotypes of snapshots.

It is also worth noting that traditional backup tools are used to backup a system and later on restore the system to the state before theback-up. In one or more embodiments, the long-term snapshot is stored asan image object in an image library; existing backup systems deal withthe concept of a file system, whereas an image is a super-set of a filesystem. An image also includes aspects of a virtual machine, such ascentral processing unit (CPU), memory configuration, and so on. An imagelibrary provides versioning and analytics capabilities.

Referring now to FIG. 22, one or more embodiments advantageously reducemigration risk by using an image library 2202. Here the “snapshot”action produces short term snapshots, so 2216-2228 are short termsnapshots. The act of “check in” into the image library 2202 produceslong term snapshots 2206, 2208, 2210. In one or more instances, thestates at critical points of time are captured to form an image versionchain (e.g., version zero 2204, version one 2206, version two 2208, andversion “n” 2210). In the case of a system malfunction, one or moreembodiments revert to the “last known good state.” One or more instancesretroactively “introspect” image versions (i.e., inspect the content ofthe system at a point of time in the past). One or more instances “diff”(i.e., carry out a comparison to identify differences) any pair ofversions at the file level to understand changes made between them.Furthermore in this regard, one or more embodiments, as part of theintrospection aspect, reconstruct an earlier state. For example, when animage is checked into the image library, the contents (meta-information)are parsed and stored in the image library and the resulting datastructure can subsequently be inspected. In the short term case(short-term snapshot such as in VMware) a rollback process can becarried out.

Still referring to FIG. 22, the process begins with an original image2212 (after physical-to-virtual (“P2V”) translation). This originalimage is imported into the image library 2202 as version zero, at 2204.An instance of the original image is started at 2230. A first adjustmentis made at 2246, to transition from instance 2230 to instance 2234.Snapshots 2216, 2218 are taken of each incremental change; i.e., ofinstance 2232 and instance 2234 (instance 2230 is simply aninstantiation of the original image after P-2-V so no snapshot isneeded, although one could be taken if desired). The snapshots are of ashort term nature. Upon completion of the first adjustment 2246,snapshot 2218 is checked into the (long term) image library as versionone at 2206. A second adjustment is made at 2248, to transition frominstance 2234 to instance 2240. Snapshots 2220, 2222, 2224 are taken ofeach incremental change, i.e., of instances 2236, 2238, 2240. Uponcompletion of the second adjustment 2248, snapshot 2224 is checked intothe image library as version two at 2208. An even further adjustment ismade at 2250, to transition from instance 2240 to instance 2244.Snapshots 2226, 2228 are taken of each incremental change, i.e., ofinstances 2242, 2244. Upon completion of the third adjustment 2250,snapshot 2228 is checked into the image library as version “n” at 2210.As indicated by the ellipsis, any desired number of adjustments can bemade. Time increases along the axis from left to right. Again, thearrows from 2232-2244 to 2216-2228 represent a short-term snapshottingprocess and the arrows from 2218, 2224, 2228 to 2206, 2208, 2210represent a long-term check-in process.

Elements 2230-2244 represent the same running instance at differentpoints of time. Each small change is snapshotted as at 2216-2228;however, only the completion of significant adjustments 2246, 2248, 2250triggers the check-in of long-term snapshots 2206, 2208, 2210. Thefrequency of long-term and short-term snapshots is thus different.

Short-term snapshots are relatively short-lived (such as the duration ofthe migration window, which typically ranges from several hours to aweekend) and contain memory states. Short-term snapshots are employedfor temporary debugging purposes, and are typically intended to bediscarded after debugging completes. Short-term snapshots occur morefrequently, thus requiring fast (on the order of seconds) operation.Short-term snapshots can be supported by a modern hypervisor; VMware isa non-limiting example (VMware software is available from VMware, Inc.,Palo Alto, Calif., USA). However, each snapshot creates a new node in asnapshot chain. In almost all implementations of snapshots in modernhypervisors, the technique of copy-on-write is used where acopy-on-write child is created on top of a read-only parent, allowing avery fast creation operation (no data copying). Subsequent writeoperations only go to the child, whereas read operations go to both thechild and the parent. When multiple snapshots are created for the sameVM, a snapshot chain is formed where each snapshot is a node in thechain. The performance of a read operation then depends on the length ofthe chain, because the hypervisor may have to traverse the chain all theway to the head, in order to retrieve the data being asked for.

In at least some instances, long chains lead to performance degradationand instability, and thus may not be appropriate for production systems.In one or more embodiments, short term snapshots 2216-2228 of virtualmachine instances 2232-2244 are taken frequently and stored in thehypervisor as virtual machine images. Long term snapshots 2204-2210 aretaken less frequently (e.g., at an initial state 2212 and afteradjustments 2246, 2248, 2250) and checked in as images (2204), 2206,2208, 2210 in image library 2202. Long term snapshots resemble long termbackups but are different in several ways.

In particular, with regard to long-term snapshots, in some instances,problems may occur long after migration (e.g., in steady-state); in suchcases it is still necessary to revert to the “last known good state.”The customer may require a snapshot of the original image beforeadjustment (e.g. for audit and/or compliance purposes). Use of an imagelibrary 2202 is more suitable in such circumstances. One or moreembodiments thus store images in an image library as persistent data forlong term preservation. In addition, the image library providesversioning and analytics capabilities for the stored long-termsnapshots. However, long-term snapshots in an image library aretypically less efficient in operation (on the order of tens of minutes).

Referring now to FIGS. 23 and 24, in one or more instances, a snapshotmanagement system (labeled in the figures as a “snapper” for brevity)2340 manages both short-term snapshots 2346 and long-term snapshots 2344(the snapshot management system also initiates rollbacks as describedbelow). In one or more non-limiting exemplary embodiments, short-termsnapshots 2346 are VMware snapshots (VM images of VM instances) thatreside on an operational repository 2468 in VMware data center 2342,while long-term snapshots 2344 are checked into the reference repository2456 of virtual image library 2202. As used herein, an operationalrepository is defined as a storage location where a hypervisor storesimage files corresponding to running, suspended, and/or stopped VMinstances. Snapshot management system 2340 creates and deletesshort-term snapshots in the form of VM instances 2470 within VMware datacenter 2342. Images of the instances are checked in and out of theoperational repository 2468 as needed. The VMware data center is usedfor short-term snapshots for rollback in the production environment2452. When a long-term snapshot is desired, an image in the operationalrepository is checked into the reference repository 2456 withinanalytics environment 2450. Indexer 2458 indexes images in referencerepository 2456, and optionally also indexes images in operationalrepository 2468 and/or VM instances 2470, to create knowledge base 2460.This knowledge base is used by engine 2462 to carry out analysis.

Furthermore in this regard, snapshot management system 2340 creates(frequently) short-term snapshots of executing virtual machine instances2470 (snapshot management system 2340 also deletes the short termsnapshots from time to time). The short term snapshots are stored asvirtual machine images of the virtual machine instances 2470 executingon the hypervisor, in repository 2468. When it is desired to create along-term snapshot (e.g., prior to an adjustment), snapshot managementsystem 2340 causes a corresponding one of the virtual machine images inrepository 2468 to be placed in reference repository 2456. On the otherhand, as seen in FIG. 25, when a rollback is desired, snapshotmanagement system 2340 checks the image out of reference repository 2456as a template, and places it into operational repository 2468 (as seenat 2572) and then reconfigures the template to match an existing VMinstance and instantiates a new virtual machine 2573 based on thetemplate, which VM image 2573 is swapped with the existing VM instance2574 for which rollback is desired.

For the avoidance of doubt, “check-in” refers to placing something intothe virtual image library and “check-out” refers to taking something outof the virtual image library (with version control); these terms are notused in reference to the VMware data store because in this contextVMware does not have version control and what occurs is simply a filecopy operation. In one or more embodiments, both long-term andshort-term snapshots are triggered by adjustments. Short term snapshotsare taken at each incremental step in an adjustment, but long termsnapshots are only taken at the beginning and end of a significantadjustment process, skipping all incremental adjustments in the middle.This is shown in FIG. 22. Other approaches could be used in otherembodiments.

Note that the VIL 2202 in FIG. 24 is the same as the Image Library 2202in FIG. 23; and the operational repository 2468 in FIGS. 23 and 24 couldbe, for example, a VMware data store.

FIG. 25 thus shows an exemplary rollback to a particular long termsnapshot. In step 1, image 2576 is located in image library 2202 basedon its long term snapshot identifier (LTS ID). In step 2, the image ischecked out as a template 2572 in operational repository 2468. In step3, the template is reconfigured to match the existing VM instance 2574,and a new VM 2573 is instantiated. In step 4, the new VM 2573 is swappedfor the existing virtual machine instance 2574.

Again, to summarize, in one or more embodiments, rolling back to a longterm snapshot involves the following steps:

-   -   1. Locating the image in the library given a long term snapshot        ID    -   2. Check out the image from the library into an operational        repository as an image template    -   3. Reconfigure template to match existing VM instance and        instantiate a new VM    -   4. Swap the image file associated with the newly created VM        instance with that of the existing VM

FIG. 26 shows an exemplary flow chart for a method to compute exactchanges made to an image during migration. In step 2602, locate the longterm snapshot of the original customer image (e.g. 2204). In step 2604,locate the long term snapshot after all adjustments are complete (e.g.2210). In step 2606, compute the difference (see example above) betweenthe two versions at the file and/or product level; then, in step 2608,return the results.

FIG. 27 shows an exemplary process flow. As seen at 2702, a snapshot istaken of an initial state, with a selective check-in (the asterisk nextto a snapshot or check-in in FIG. 27 denotes a selective snapshot or aselective check-in as the case may be). Again, a snapshot creates shortterm snapshots, whereas check-in creates long term snapshots. In 2704, afirst adjustment is made (e.g., adjustment 2222 in FIG. 22). In decisionblock 2706, a determination is made (manually and/or computer-aided) asto whether the first adjustment was successful. If not, a selectivesnapshot and selective check-in are made in step 2708, and a rollback tothe previous configuration is carried out in step 2710, with anyrequired manual remediation carried out in step 2712. The firstadjustment can then be re-tried if desired. On the other hand, if thefirst adjustment was successful, as seen at 2714, a snapshot is taken ofthe updated state, with a selective check-in. A second adjustment isthen made in step 2716 (e.g., adjustment 2226 in FIG. 22). In decisionblock 2718, a determination is made as to whether the second adjustmentwas successful. If not, a selective snapshot and selective check-in aremade in step 2720, and a rollback to the previous configuration iscarried out in step 2722, with any required manual remediation carriedout in step 2724. The second adjustment can then be re-tried if desired.On the other hand, if the second adjustment was successful, the processcan continue; for example, with a snapshot of the further updated stateand a selective check-in, followed by any further adjustments (notshown).

One or more embodiments thus advantageously provide a system thatreduces risk in migration by using a combination of short term and longterm snapshots to systematically capture system states and supportroll-back to any snapshot. One or more instances provide a method forinitiating short term and long term snapshots and separating them, aswell as Virtual Image Library-based (VIL-based) long term snapshots. Asseen in FIG. 25, one or more embodiments provide a method for rollingback to a long term snapshot. One or more embodiments permit comparisonof long term snapshots at the product and/or file levels. Further, asseen in FIG. 26, one or more instances provide a method for computingthe product-level and file-level changes made to the custom image duringthe migration process, the output of which could serve as an auditrecord for clients that desire same. Even further, as seen in FIG. 27,one or more embodiments provide a process that integrates snapshot androllback with each risky operation (e.g., adjustments 2222, 2226, 2230)on a VM.

It is worth noting that, while the idea of a checkpoint has been aroundfor a long time, it is mainly used to periodically save the states of along running system so that if the system fails it can resumecomputation from the last checkpoint rather than starting from time zero(as opposed to being used for cloud migration, as in one or moreembodiments).

Given the discussion thus far, it will be appreciated that, in generalterms, an exemplary method, according to an aspect of the invention,includes the step of, during a process of migrating a source system intoa standardized virtual environment, snapshotting virtual machineinstances 2470 of the source system executing in a hypervisor 2342 asvirtual machine images in an operational repository 2468 of thehypervisor. The virtual machine images in the operational repository areshort-term snapshots 2216-2228. This step can be carried out, forexample, by the snapshot management system 2340 invoking or issuing acommand to the hypervisor (VMware is a non-limiting example of thelatter). The method also includes, from time to time during themigration process, creating long-term snapshots 2344 of the sourcesystem. The long-term snapshots are created by checking given ones ofthe virtual machine images from the hypervisor operational repositoryinto an image library 2202 as image objects (e.g., in referencerepository 2456). This step can be carried out, for example, by thesnapshot management system 2340 invoking or issuing a command to thevirtual image library 2202.

Furthermore with regard to the step of snapshotting, snapshottingmechanisms per se are typically provided by known hypervisors. However,in one or more embodiments, snapshot management system 2340 issues acommand to or invokes the hypervisor. That is to say, existinghypervisors have snapshotting capability per se but in one or moreembodiments, a new piece of code, namely, snapshot management system2340, is provided. Referring to the exemplary details in FIG. 28, system2340 has logic to determine when to issue commands. In one or moreembodiments, snapshot management system 2340 has a data structure ormapping table or the like that can map a given VM ID into a long-termsnapshot. System 2340 also has logic such that when asked to roll backto a long term snapshot, system 2340 will know from the mapping whichversion of the long term snapshot is to be obtained from the imagelibrary, checked out, and swapped as shown in FIG. 25. Snapshotmanagement system 2340 is thus a piece of software that implements thelogic in FIGS. 23 and 25 based on external input. As seen in FIG. 23,inputs include a command to take a long-term snapshot, a command to takea short-term snapshot, or a command to roll back to a previous state.API manager 2802 validates the arguments of input commands and createsand connects to any required services. Orchestrator 2804 decomposes thecommands as needed to a sequence of commands that can be understood bythe pertinent hypervisor and virtual image library (in this non-limitingexample, VMware vCenter and IBM VIL, respectively). Orchestrator 2804also orchestrates command execution and retrieves and processes resultsand errors.

For the taking of a short-term snapshot, orchestrator 2804 invokesVMware program API 2806 or other VMware adapter after the appropriatechecking and conversion to an object are carried out. For the taking ofa long-term snapshot, virtual image library query executor 2808 isemployed to interact with image library 2202 as shown in FIG. 25. VMDKswap adapter 2810 builds and executes the VMDK swap command to implementthe swapping process shown in FIG. 25.

Thus, the step of creating the long-term snapshots is carried out by theVIL 2202 under control of snapshot management system 2340. One suitablevirtual image library is the IBM SmartCloud Provisioning Virtual ImageLibrary available from International Business machines Corporation,Armonk, N.Y., USA.

It will be appreciated that a cloud, such as an MIaaS cloud or othercloud, is one non-limiting example of a standardized virtualenvironment.

In some cases, the creating of the long-term snapshots from time-to-timeincludes creating the long-term snapshots prior to significantadjustments (e.g., 2222, 2226, and 2230 in FIG. 22) during the migrationprocess.

Some cases, as best seen in FIG. 25, further include initiating arollback. This can be done by:

-   -   locating a given one of the image objects 2576 in the image        library 2202, as per step 1;    -   checking the given one of the image objects out of the image        library as a template 2572, as per step 2;    -   placing the template 2572 into the hypervisor operational        repository 2468; and    -   instantiating the template from the hypervisor operational        repository as a rolled-back virtual machine instance in the        hypervisor (where it replaces an existing VM instance 2574 that        was problematic, so that rollback to a previous state was        desired), as per steps 3 and 4 and locations 2573, 2574.

As noted, in one or more embodiments, such rollbacks can be initiatedduring a steady state condition after the migration.

As shown in FIG. 26, in some cases, changes made during the migrationcan be determined by locating a first given one of the image objects inthe image library, as per step 2602. The first given one of the imageobjects corresponds to one of the long-term snapshots associated with anoriginal customer image of the source system (e.g., 2204). A furtherstep in determining changes includes, as per step 2604, locating asecond given one of the image objects in the image library. The secondgiven one of the image objects corresponds to one of the long-termsnapshots associated with a customer image of the source system afterthe significant adjustments are complete (e.g., 2210). In step 2606, thedifferences between the first and second given ones of the image objectsare computed (e.g., with engine 2462—in some cases, a “diff” feature ofthe aforementioned IBM SmartCloud Provisioning Virtual Image Library canbe employed). An even further step includes making a representation ofthe differences available to a human operator (e.g., via a suitablegraphical user interface (GUI) displaying same on a display 24 or thelike). The differences that are computed can be, for example, file-leveldifferences and/or product-level differences.

In some cases, a further step can include assigning a version number toeach of the long-term snapshots as shown in FIG. 22; i.e., V.1, V.2, . .. , V.n. The result is a version chain of images, each corresponding tosignificant adjustments made; effectively providing a source controlsystem.

In another aspect, an apparatus includes a memory (e.g., RAM 30, cache32); and at least one processor 16, coupled to the memory, and operativecarry out or otherwise facilitate any one, some, or all of theaforementioned method steps. Optionally, the apparatus further includesa plurality of distinct software modules 42. Each of the distinctsoftware modules is embodied on a computer-readable storage medium, andthe distinct software modules include a snapshot management systemmodule, a hypervisor module, and a virtual image library module, asdiscussed elsewhere herein. The snapshot management system moduleoptionally includes one, some, or all of the sub-components in FIG. 28.

Replacing Virtual Machine Disks

A virtual machine (VM) is a software implementation of a computer thatexecutes programs like a physical machine. Virtual machines may have oneor more virtual disks associated therewith. One or more embodimentsadvantageously facilitate the growth of cloud computing by providing oneor more of:

-   -   techniques to migrate one or more disks associated with a source        virtual machine (image or instance) into a target virtual        machine;    -   techniques to restore a virtual machine using a different set of        virtual disks; and/or    -   techniques that can accomplish migration and/or restoration        without the need to alter the unique IDs associated with a        virtual machine.

Advantageously, one or more embodiments provide techniques for replacingthe disks associated with an existing virtual machine with disks ofanother virtual machine, or images thereof, without impactingfunctionality or the identity of the virtual machine. Indeed, one ormore embodiments provide techniques to support the ability to replacethe disks associated with a virtual machine with the disks associatedwith another virtual machine or image; techniques which determine thecompatibility of the virtual machine configurations and their disks;and/or techniques which ensure that the resulting virtual machinecontinues to function after the disks have been replaced.

Furthermore in this regard, and referring now to FIG. 34, in at leastsome embodiments, there are four states overall, as listed below. An“image” is offline/dormant/static, as in “image” of a virtual machine.An instance is a running virtual machine or registered to be able to runin a virtual machine, as in an “instance” of an image. As in FIG. 34, a“virtual machine image” or “image” or “virtual machine template” 3402includes a virtual disk 3406 containing at least an operating system,and virtual hardware suggestions 3408 such as CPU, memory, and/or disk.A “virtual machine” or “instance” or “instance of an image” 3404includes 3406 and 3408, as well as virtual hardware allocations 3410 ofCPU, memory, and/or disk, and a hypervisor of virtual machine runtime3412. The aforementioned four states include:

-   -   1. an image which is existing independent of a hypervisor (i.e.        file on a file system)—Virtual Machine Image    -   2. an image which is registered to a hypervisor (i.e. template        or clone source)—Virtual Machine Image    -   3. a virtual machine registered to a hypervisor but is not        running (i.e. powered off virtual machine)—Virtual Machine    -   4. a virtual machine registered to a hypervisor and is running        (powered on virtual machine)—Virtual Machine

The replacing of the target could occur from any one of these sourcestates. Therefore, in the most general case, the source can, but neednot, be an “image” format as in (1) and (2) or it could be transporteddirectly as per (3) or (4).

Furthermore, one or more embodiments provide a systematic way to enablea cloud to adopt an existing server without the need to migrate theapplication to a net new cloud instance; and/or a rule system to capturewhich attributes of a source and a target virtual machine should bepreserved in order to maintain virtual machine functionality and to beundetectable to the parent hypervisor and/or cloud.

In at least some cases, virtual machines can be replaced without makingit known to external elements, such as, for example, a cloud managementstack. This capability allows for substantial changes to be made to avirtual machine (for example, replacing the contents of all disks)without the hypervisor or dependent management stack being aware of thechange. One or more embodiments can be used, for example, to migrate anexternal virtual machine into a managed cloud, thus enabling the cloudto import existing virtual machines. Furthermore, one or moreembodiments can be used to restore a virtual machine to a previousstate.

Attention should now be given to the system diagram of FIG. 29. Notesource virtual machine 2901 with one or more disks such as disk 1,numbered 2906, and disk 2, numbered 2908. Disks 2906, 2908, 2910, 2912are all virtual disks. Virtual disks are discussed further in connectionwith, e.g., FIG. 36. The system also includes a virtual machine diskreplacer such as image replacer 2902, which operates in accordance withmerger rules 2914. It is desired to replace Disk 1 and Disk 2, 2910,2912, on target VM 2903 with disks 2906, 2908. The disks 2910, 2912 alsorepresent the after-migration state; that is, prior to migration, Disk 12910 and Disk 2 2912 are in an original state and after migration theyhave effectively been replaced with disks 2906, 2908 respectively. Thetarget virtual machine 2903 is managed by hypervisor 2904 and theoverall target cloud environment is managed by cloud management software2905.

Referring now also to FIG. 30, cloud hypervisor 3001 (same as hypervisor2904) is a hypervisor which is managed by the desired target cloud; allinstances running within the hypervisor 3001 are assumed to be managedby the cloud. Note that in FIG. 29, the source is depicted external tothe cloud hypervisor, while in FIG. 30, both source and target arelocated on the same hypervisor. These scenarios are different but bothare valid and possible. The customer image is imported into the cloudenvironment and is the source 3002 in the technique shown in FIG. 30;cloud image 3003 is the target. As noted elsewhere, an image of sourceis not always required. Source 3002 is implemented on virtual machine3004. Virtual disk descriptor 3006 is a meta-file describing theattributes of the virtual disk(s) 3008, which are the actual blockallocations where the disk content is stored.

The cloud adopter 3010 implements one or more techniques describedherein in accordance with merge rules 2914. Merge rules 2914 in FIG. 30and merger rules 2914 in FIG. 29 are the same. Element 3010 is the sameas element 2902; element 3004 is the same as element 2901; and element3005 is the same as element 2903. Disks 3008 include one of 2906, 2908.Disks 3009 include one of disks 2910, 2912. Note that FIG. 36 providesadditional details on the relationships of virtual disk descriptors tovirtual disk extents to virtual disks. The merge rules 2914 providespecific rules about which attributes of the source virtual diskdescriptor(s), the target virtual disk descriptor(s) and process areincluded in the final target disk descriptor 3007. The merge rulesensure that the resulting virtual machine 3005 executes and that thecloud management layer and hypervisor 3001 cannot notice a difference.The virtual disks 3009 are the actual block allocations where the diskcontent is stored in the new virtual machine 3005.

With continued attention to FIGS. 29 and 30, consider also FIG. 31,which depicts a process of replacing a set of disks of a VM 2903, 3005with those of a source virtual machine 2901, 3004. In step 3101,identify the receiving cloud instance 2903, 3003. In one or moreembodiments, the target is a virtual machine (instance) that is in apowered-off state. In step 3102, identify the customer source 2901,3002. In step 3103, compare the virtual resources of VM 2901, 3004 withthose of VM 2903, 3005. In step 3104, determine if the resources arecompatible; if not, reject the proposed replacement at 3105 and then theprocess ends at 3111.

Reference should now be had to FIGS. 35 and 36. Note VM image 3502. In ahypervisor there is typically an overall VM description (file) 3504setting forth all the virtual hardware characteristics of the virtualmachine. In some cases, as shown in FIG. 35, all pertinent diskinformation regarding virtual disks 3506 is contained in this singlemaster file. In other cases, as seen in FIG. 36, the master file 3604references other files (descriptors) 3610, 3612 which include thedetails of one or more virtual disks 3614, 3616, 3618.

FIG. 36 is thus an example of a virtual machine image or instance whichhas one level of indirection between the VM resource descriptor and theactual virtual disk. The Virtual Disk Descriptor containsmeta-information about one or more backing disks. This example wouldpresent two disks to the virtual machine operating system but isrealized by three separate virtual disk files.

Returning now to FIG. 31, if the virtual resources are compatible, asshown at the YES branch of decision block 3104, merge the source virtualresource descriptors 3112 (e.g., virtual disk descriptors 3006) and thetarget virtual resource descriptors 3113 (e.g., virtual disk descriptors3007) in step 3106. Furthermore in this regard, elements 3007 and 3113represent the target disk descriptor before the replacement occurs.After the merge and replace, element 3007 becomes an updated versionwhich is a combination of parameters for the source and the target. Partof step 3108 includes the step to write the new target disk descriptor3007. See FIG. 32.

In decision block 3107, determine if the merge of the virtual resourcedescriptors in step 3106 was successful; if not, the process ends at3111. On the other hand, if the merge of the virtual resourcedescriptors in step 3106 was indeed successful, proceed to step 3108 andreplace the virtual disk as shown at 3303 in FIG. 33. In decision block3109, determine whether the source VM has more disks; if yes, repeatsteps 3106-3109 as needed; if not, update the overall instancedescriptor in step 3110. Step 3110 is optional and depends on whetherthe approach of FIG. 35 or FIG. 36 is used by the VMs that are beingoperated on. Processing ends at 3111.

Furthermore with regard to FIGS. 35 and 36, implementations can differin that all virtual machine resource information (including disks) canbe stored in a single file as in FIG. 35 or it can be separated intomany files as in FIG. 36. The approach is dependent on the hypervisorand has to do with the level of decoupling of components (i.e. for theexamples with virtual disk descriptors there is a reference in theoverall virtual machine definition linking to those descriptors, thenmore information in the descriptors about the actual characteristics ofthe underlying disk). Step 3110 is appropriate where the approach ofFIG. 36 is utilized.

FIG. 32 presents exemplary details of the merging step 3106. In step3203, access the source descriptors 3112. In step 3204, access thetarget descriptors 3113. In step 3205, examine an attribute. In decisionblock 3206, determine at least whether the attribute in question iscritical to the source, based on the merge rules 2912.

In this regard, the merge rules 2912 are specific to the targethypervisor (non-limiting examples include VMware virtualization softwareavailable from VMware, Inc., Palo Alto, Calif., USA; KVM software (forKernel-based Virtual Machine) (available from RedHat, Inc. Raleigh,N.C., USA), Xen software (available from Citrix Systems, Inc., Ft.Lauderdale, Fla., USA), and so on). In step 3205 and decision block3206, a number of determinations are made as attributes of both thesource and target environments are examined. Steps 3206-708 arediscussed further below with regard to FIG. 37. With regard to sourceattributes, it may be determined, for example, that Attribute A of thesource must persist to ensure continued virtual machine functioning inthe target cloud. Examples of such source attributes include the Virtualdisk input-output (IO) controller, the block size, the number of blocks,and so on. The same are written to the “new” target descriptor (which isa combination of both source and target parameter/values) in step3207—see discussion of FIG. 37 below. With regard to target attributes,it may be determined, for example, that Attribute B of the target mustpersist to ensure that the cloud successfully adopts the virtual machine(nether hypervisor nor cloud notices a difference). Examples of suchtarget attributes include the virtual disk unique identifier. The sameare written to the new merged descriptor in step 3208. Processing thenflows to step 3210.

In decision block 3210, check to see if there are additional attributes;if so, loop back to step 3205 and repeat the process until all theattributes have been examined. If there are no more attributes, theprocess ends at step 3211 and flow proceeds to step 3107 in FIG. 31.

Considering now FIG. 37, source virtual machine descriptor 3751 includesParameters 1-4 with respective values A, B, C, and D. Target virtualmachine descriptor 3753 includes Parameters 1-3 with respective valuesX, Y, and Z. As indicated at 3755, the logic in step 3206 is applied foreach parameter in the source and target descriptors, i.e., Parameters1-4. In step 3206, target parameters dominate unless the sourceparameter is needed to maintain functionality or compatibility. Thus, bydefault, all target parameters are retained in updated target virtualmachine descriptor 3757, but only the needed source parameters areretained. In the example in FIG. 37, the source parameter values forparameters 1, 3, and 4 were necessary while the target value of “Y” forparameter 2 was retained by default because that source parameter wasnot needed to maintain identity or functionality. It should be notedthat target parameters are assumed to all be compatible as they were theinitial values for the existing virtual machine which presumablyfunctioned and was properly known to the hypervisor/management layer.

Thus, one or more embodiments provide a system and method to support theability to replace the disks associated with a virtual machine with thedisks associated with another virtual machine or image; a method whichdetermines the compatibility of the virtual machine configurations andtheir disks; and/or a method which ensures that the resulting virtualmachine continues to function after the disks have been replaced.

Referring now to the system diagram of FIG. 33, one or more embodimentsconsider an existing physical or virtual server 3301 that does notreside within the managed cloud; rather, server 3301 resides in existingsource environment 3350. Server 3301 has existing disks 3351. As seen at3302, server 3301 is converted to an image 3352. Thishypervisor-compatible image is then transported into the target cloud3354. During cloud adoption process 3303, merger and replacement of thecloud provisioned image with the customer image is carried out. Thisprocess can, in some instances, be facilitated by migration engineer3353. The cloud is unaware of any significant change to a virtualmachine (here, VM7 numbered 3365) running under its control, asindicated at 3304.

Target cloud 3354 includes a management layer 3355 (which in at leastsome instances can be similar to layer 64 described above). Cloud user3367 interacts with management layer 3355. Management layer 3355 manageshardware and software of the cloud environment 3354 including one ormore hypervisors such as 3356, 3357, 3358. The hypervisors in turnmanage one or more virtual machines 3366; in the example of FIG. 33,Hypervisor 1, numbered 3356, manages VMs 1-3 numbered 3359-3361;Hypervisor 2, numbered 3357, manages VM 4 numbered 3362; and Hypervisor3, numbered 3358, manages VMs 5-7 numbered 3363-3365.

Thus, one or more embodiments provide a method which allows a non-cloudprovisioned image to be adopted by the cloud and be treated as any othercloud provisioned instance; a process which defines how to move anexisting physical or virtual server into a cloud without formal support;a system that supports merging virtual machine descriptors; and/orreplacing target image disks with source image disks; and/or a method ofmerging virtual resource descriptors. This latter method can include,for example, retrieving virtual resource descriptor(s) from a source andtarget image; comparing the attributes of each virtual resourcedescriptor; and/or merging both descriptors into a third descriptorwhich is compatible with the target virtual machine configuration, thetarget hypervisor, the target virtual machine operating system and thetarget cloud.

One or more embodiments thus provide the capability to replace one ormore virtual disks associated with a source virtual machine over thesame number of virtual disks associated with a target virtual machine.This capability enables the ability to migrate either a virtual machineor virtual machine image into an existing virtual machine definition.This is relevant, for example, in a cloud or managed cloud scenariowhere the identity and features of the virtual machine are managed at ahigher level (i.e. to track capacity, licensing, and so on). If theidentity changes, the management layer would lose track of the system.Another scenario allows for the restoration of a virtual machine to aprevious state by allowing its current set of virtual disks to bereplaced by a previously captured set of virtual disks. A furtherpossibility allows the re-use of virtual machine “containers” by simplyreplacing the virtual disk contents as opposed to creating entirely newcontainers each time.

Given the discussion thus far, it will be appreciated that, in generalterms, an exemplary method, according to an aspect of the invention,includes the step 3106 of merging at least one target virtual diskdescriptor 3007, 3113 that describes at least one virtual disk 2910,2912, 3009 associated with an existing target virtual machine 2903, 3005in a target virtualized environment with at least one source virtualdisk descriptor 3006, 3112 that describes at least one virtual disk 3352associated with a source. The merging is carried out in order to obtainat least one merged virtual disk descriptor (also represented by 3007;i.e., element 3007 represents the descriptor before the merge and alsoafter the merge at which point it has some source parameters). The atleast one merged virtual disk descriptor is compatible with the targetvirtualized environment. In some cases, step 3106 can be carried outusing a “MergeDiskMetaData” sub-module 3913 of a swap module 3901,executing on at least one hardware processor, as described below inconnection with FIG. 39. A further step 3108 includes replacing the atleast one virtual disk associated with the existing target virtualmachine in the target virtualized environment with the at least onevirtual disk associated with the source, in accordance with the mergedplurality of virtual resource descriptors. In some cases, step 3108 canbe carried out using a “PutDisk” sub-module 3915 of a swap module 3901,executing on at least one hardware processor, as described below inconnection with FIG. 39.

Furthermore in this regard, in FIG. 39, note swap module 3901.Preparation sub-module 3902 ensures that the source and target VMs arein a state wherein they can be operated upon (image versus instance).Any needed preparations are carried out by prepSource sub-module 3903and prepTarget sub-module 3905, for the source and target, respectively.CheckCompatibility sub-module 3907 makes sure that the source and targetare compatible. SwapDisks sub-module 3909 and replaceDisk sub-module3911 include control logic to implement the looping in FIG. 31 throughthe tasks assigned to sub-modules 3913 and 3915; i.e., steps 3106 and3108.

TransformDisk sub-module 3917 addresses issues if the source does notmatch the target specification; it transforms the actual virtual disk tomake it indistinguishable. One example is if the source and targetvirtual disks are of different sizes. This will typically not impact thehypervisors but could cause issues with future operations such as“extend disk.” The updateVMSpec sub-module 3919 carries out the optionalstep 3110 associated with FIG. 36-type configurations. Hypervisoradapter module 3930 merges in each of the functions to the APIs 3931exposed by the hypervisors 3932, 3933, 3934; namely, the ability to copyfiles, move files, obtain descriptors, and update descriptors. Theellipses with regard to 3933, 3934 refer to “operation implementation”as spelled out in 3932.

Furthermore with regard to prepare block 3902, refer to FIG. 38. Theprepare function obtains or accesses the source image 3802, sourcephysical machine 3804, or source virtual machine 3806 and brings same toa state where the replace operation can be carried out. Source image3802 can simply be deployed to a VM under a hypervisor, as shown at3812. Source physical machine 3804 can be converted to an image in thecase of no hypervisor, as shown at 3808, or converted to a VM in thecase of a hypervisor, as shown at 3810. Source VM 3806 can also beconverted to a VM as in 3810. In each case, flow proceeds as appropriateto the target VM disk replacement at 3814.

The modules and/or sub-modules shown in FIGS. 38 and 39 can be writtenin a variety of languages; Perl is a non-limiting example.

In some cases, the target virtualized environment is a target cloudenvironment. One or more embodiments are believed to be especiallyuseful with respect to clouds because clouds are sensitive to thechanging of identity.

One or more embodiments thus address the replacement of virtual diskswhich is supported by the merging of meta-data about those virtualdisks.

In some instances, the source is a customer source outside the targetcloud environment, and the replacing includes migrating the at least onedisk associated with the source to the at least one disk associated withthe existing target virtual machine, as depicted, e.g., in FIG. 33.

In at least some embodiments, an additional step 3103 includes comparingvirtual resources of the at least one disk associated with the existingtarget virtual machine and the at least one disk associated with thecustomer source outside the target cloud environment. In such cases, themerging is in response to the comparing of the virtual resourcesindicating compatibility thereof, as per the YES branch of decisionblock 3104.

In at least some embodiments, an additional step 3107 includes checkingfor success of the merging step. In such cases, the replacing in isresponse to the checking indicating the success of the merging step, asper the YES branch of decision block 3107.

With regard to the decision in decision block 3104, one or moreembodiments make use of a data repository 3199 which tracks knowncompatibilities. These compatibilities, for instance, would compare theIO adapter or the like across the source and target to determine if thesource operating system would be able to function with the targetadapter (if different). In some embodiments, a check is also made toensure that the number of disks matches (i.e. might be unable to merge asource with two disks into a target with one disk). Overall, the contentof database 3199 may, for example, be mined from the technicallimitations associated with both the operating system and softwarecontained within the virtual machine/image as well as any compatibilityissues at the hypervisor level (i.e. maximum disk size, maximum numberof disks, and so on).

An analogous approach may be used to develop a data store (omitted fromfigure to avoid clutter) on which the decision in block 3107 may bebased.

As indicated by decision block 3109, in some cases, the merging andreplacing steps are repeated for one or more additional source virtualdisks. This overall flow can operate on each virtual disk associatedwith the source image/virtual machine. The decision block 3104 check isa go/no-go before any changes are made. The 3106, 3108 processes are theactual updating of the disk meta-data and replacing of the disk.

In at least some cases, an additional step 3110 includes updating anoverall instance descriptor. Again, step 3110 is optional and depends onwhether the approach of FIG. 35 or FIG. 36 is used by the VMs that arebeing operated on.

In some cases, the merging step 3106 includes, as seen at 3205,examining at least one source attribute associated with the at least onesource virtual disk descriptor and examining at least one targetattribute associated with the at least one target virtual diskdescriptor. A further step 3206 includes applying a plurality of mergerules 2912 to the at least one source attribute and the at least onetarget attribute to obtain the at least one merged virtual diskdescriptor. The merge rules persist, in the at least one merged virtualdisk descriptor, source attributes needed to ensure continued virtualmachine functioning in the target cloud and target attributes requiredfor the target cloud to successfully adopt the virtual machine.Furthermore in this regard, in one or more embodiments, there aredescriptors for the source, the target before the merge, and the targetafter the merge. The source and target merge to create an updatedtarget. The target virtual machine continues to function properly asdoes the runtime of the virtual disks which have been replaced into it.

Non limiting examples of merge rules used in applying step 3206 includepersisting a virtual disk input-output controller of the at least onevirtual disk associated with the source; persisting a block size andnumber of blocks of the at least one virtual disk associated with thesource; and persisting a virtual disk unique identifier of the at leastone virtual disk associated with the existing target virtual machine.

In some cases, a source disk image is already available. Also, asdiscussed above, the replacing of the target could occur from any one ofsource states (1)-(4), and in the most general case, the source can, butneed not, be an “image” format. In some cases, as seen at 3302, anadditional step includes converting a source instance to obtain a sourcedisk image 3352.

In at least some cases, the target virtual machine 2903, 3005 has atarget virtual machine configuration; the target virtual machine 2903,3005 is hosted on (a guest of) a target hypervisor 2904, 3001; and thetarget virtual machine 2903, 3005 optionally has a target operatingsystem. In the merging step 3106, the compatibility with the targetvirtualization environment includes at least compatibility with thetarget virtual machine configuration and the target hypervisor.Optionally the compatibility with the target virtualization environmentfurther includes compatibility with the target operating system.

With regard to the target virtual machine not having an operating systemin some cases, one example is a PXE boot system or system booting fromCD/DVD; the same could have all of its disks replaced without impactingthe “operating system.”

In addition to migration applications, in some cases, the source 2901 isa back-up source; and the replacing includes restoring the at least onedisk (e.g., 2910 or 2912) associated with the existing target virtualmachine using the at least one disk image associated with the back-upsource.

As noted elsewhere, in one or more embodiments, there is no change tofunctionality and identity of the VM 2903, 3005, 3365, and/or theprocess is not detectable to the parent hypervisor 3358 and cloudmanagement 3355. It should be noted that hypervisors typically have theconcept of a unique identifier for the virtual machine that is notduplicated within the virtualization environment. The skilled artisanwill be familiar with same, for example, from VMware and KVM (forKernel-based Virtual Machine, a full virtualization solution for Linuxon x86 hardware containing virtualization extensions). The VMwareVirtual Machine UUID (backed by a field called uuid.bios in the virtualmachine descriptor file—a .vmx) is a non-limiting example of a uniqueidentifier. This, in one or more embodiments, any type of uniqueidentifier or associated data stored in the hypervisor or managementstack remains consistent and unchanged. The operation/behavior of thereplaced target disks is equivalent to that of the original runtime withthe source disks. Thus, in some cases, when replacing the at least onevirtual disk associated with the existing target virtual machine in thetarget virtualized environment with the at least one virtual diskassociated with the source, a unique identifier of the existing targetvirtual machine is maintained prior and subsequent to the replacement.

In another aspect, an apparatus includes a memory (e.g., RAM 30, cache32); and at least one processor 16, coupled to the memory, and operativecarry out or otherwise facilitate any one, some, or all of theaforementioned method steps. Optionally, the apparatus further includesa plurality of distinct software modules 42. Each of the distinctsoftware modules is embodied on a computer-readable storage medium, andthe distinct software modules include a MergeDiskMetaData module and aPutDisk module; as discussed elsewhere herein.

Adjustment to Managed-Infrastructure-as-a-Service Cloud Standard

A hardware infrastructure as a service cloud (HIaaS Cloud) provides barebone virtual machines as a service. It may also provide an operatingsystem and applications; however, support is typically not provided forany software installed on the virtual machine (VM). A non-limitingexample is the Amazon Elastic Compute Cloud (Amazon EC2) available fromAmazon Web Services LLC Seattle, Wash., USA. A managed infrastructure asa service cloud (MIaaS Cloud) provides full service virtual machines.The service contract includes providing software services for theunderlying virtual machine. These services include software upgrades,patch support, support for compliance, license management, and the likefor the provided software infrastructure. A non-limiting example is theIBM SmartCloud Enterprise+ also known as IBM SCE+, cloud environmentavailable from International Business Machines Corporation, Armonk,N.Y., USA. Image-based migration uses customer images for migration ofthe application to the cloud. This approach minimizes expensiveapplication re-installation. A cloud standard is the minimum set ofrequirements needed to be met by a customer image to be run and managedin cloud.

One or more embodiments advantageously provide a system and method forrapid, reliable, and reduced cost adjustment to MIaaS cloud standard.One or more embodiments take an arbitrary customer instance and performa set of changes so that the MIaaS management layer can manage thecustomer application exactly as it would manage an application createdfrom its own golden masters (reference models from which copies aremass-produced). One or more embodiments provide a process which is rapid(the end-to-end duration of standardization is small (e.g., <4 hours));exhibits reduced cost (the amount of time spent by a migration engineeris quite small (e.g., <30 minutes); and reliable (images coming out ofthe process are standard with high reliability and meet all customerpreferences). Furthermore, one or more embodiments provide a two-stepprocess wherein customers and cloud engineers formulate a flexiblestandardization plan in line with customer preferences and cloudstandard, and wherein an automated framework executes the plan in areliable fashion in conformance with the rules.

In one or more embodiments, rules are used to uniformly encodeadjustment recipes across various kinds of images; image adjustments areused for standardization; and/or a generic orchestration framework isused to deal with multiple types of adjustment actions.

Currently, with regard to attempts to standardize migration to MIaaSenvironments, it should be noted that an MIaaS delivery model isdependent on having pre-fabricated virtual machine images, which meetall the services requirements. Currently, standardization forimage-based migration is manual and suffers from being time consuming,costly, and unreliable. Current techniques are time-consuming because alarge number of long running steps are needed. Current techniques arecostly because all steps are performed manually. Furthermore, currenttechniques are unreliable; furthermore in this regard, since sourceinstances are different, a migration engineer needs to manually identifythe right set of steps to be performed on each source instance. Theresult is that required steps may be missed; unwanted steps may beperformed and corrupt the instance; and/or many decisions are nottechnical and need to be taken in consultation with the customer. Thatis to say, the migration engineer may not be suited for deciding on thefly.

One or more embodiments advantageously provide a rapid standardizationapproach. One or more embodiments define a generic framework, as seen inFIG. 40, in which standardization plans can be injected. Note adjustmentframework 4002; supporting tools 4004 including individual tools 4020,4022, 4024; and adjustment zone 4006. Adjustment plans 4018 canencompass a wide variety of adjustment actions. Each type of action isorchestrated by its orchestrator 4012, 4014, 4016; the orchestratorsoperate under control of adjustment choreographer 4008. New actions canbe added to an existing plan, allowing the framework to be extensible.Adjustment actions can also include offline adjustments, which do notrequire an instance to be running.

New orchestrators 4012, 4014, 4016 and actions can be registered in theadjustment plan 4018 (for example, using a suitable plan manager 4010).Each orchestrator 4012, 4014, 4016 may interact with the virtualmachines 4030, 4032, 4034 (online), image repository 4028 (offline),virtualization manager 4026, or any other supporting tools (e.g., IBMTivoli® Endpoint Manager (TEM) server, IBM Tivoli Provisioning Manageravailable from International Business Machines Corporation, Armonk,N.Y., USA; VMware vCloud Director available from VMware, Inc. Palo Alto,Calif. USA).

One or more embodiments provide a rapid standardization system andmethod which utilizes offline adjustments. Offline adjustments are filesystem patches that can be applied to a virtual machine image.Adjustments will make changes to the image to meet the cloud standard(e.g., install a Secure Shell (SSH) service). Offline adjustments can beapplied in parallel and without using up any compute resources, thusenabling rapid adjustments. Offline adjustments include simple filesystem copies or other operations not requiring the VM to be activated.This takes much less time than actual execution of theinstall/configuration steps (again, enabling rapid adjustment). Offlineadjustments can be applied without booting up the image and do not neednetwork access to the image. This advantageously solves thechicken-and-egg problem wherein access to the VM in cloud requiresconfiguration (thus removing manual steps).

The flow chart of FIG. 41 shows the flow of a sample offline adjustment.The flow chart begins at 4102. In decision block 4104, determine, forexample, whether cygwin/ssh service exists. In this regard, Cygwin is aUnix-like environment and command-line interface for Microsoft Windows.Cygwin provides native integration of Windows-based applications, data,and other system resources with applications, software tools, and dataof the Unix-like environment. Thus it is possible to launch Windowsapplications from the Cygwin environment, as well as to use Cygwin toolsand applications within the Windows operating context.

In this example, as seen at the “YES” branch of block 4104, if thecygwin/ssh service already exists, further processing is not needed soproceed to the end and 4106. On the other hand, if the cygwin/sshservice does not already exist, as seen at the “NO” branch of block4104, in step 4108, power of the virtual machine and mount the virtualmachine. In step 4110, copy the cygwin manifest onto the image. In step4112, copy the required public keys onto the image. In step 4114, updatethe registry to run the script on the first boot of an instance. In step4116, dismount the virtual machine and power on the virtual machine. Instep 4118, the script to enable the ssh service now executesautomatically; proceed to end step 4106. It should be emphasized thatFIG. 41 is but one specific detailed example demonstrating how anoffline adjustment can be carried out in one or more embodiments.Furthermore in this regard, as noted, offline adjustments are filesystem patches that can be applied to a virtual machine image;implementing cygwin/ssh service is thus a non-limiting specific exampleof many kinds of offline adjustments that can be carried out in one ormore embodiments.

Reference should now be had to FIGS. 42 and 43. One or more embodimentsprovide reduced cost standardization via an automated adjustment engine4302. One or more embodiments include an adjustment orchestrator 4304and/or 4310. The orchestrator 4304 and/or 4310 defines a set of phaseswhere a dependent phase is executed only after all its antecedent phaseshave been executed. Steps in each phase are encapsulated as a script.Scripts can be run on the adjustment engine 4302, on target virtualmachines, or on any other management tool (e.g., integrated with vCenter(VMware vCenter Server provides a centralized and extensible platformfor managing virtual infrastructure, and is available from VMware, Inc.of Palo Alto, Calif., USA) or TEM). In one or more embodiments, a singleuser interface 4302 is provided for all kinds of images (e.g., Windows,Linux, AIX). Furthermore in this regard, in an exemplary embodiment,element 4302 is the adjustment portal and the master choreographer 4008,which decides the order in which the individual orchestrators 4012,4014, 4016 will be invoked. The adjustment engine is the sum of allcomponents. The portal is an optional entity in element 4302 as thechoreographer can be invoked directly using a programmable API. Insummary, in the non-limiting example, element 4302 equals thechoreographer plus, optionally, the portal. In one or more embodiments,multiple images can be adjusted in parallel (this reduces the amount oftime spent per image being standardized).

One or more embodiments provide reliable standardization. One or moreembodiments provide a flexible rule framework that takes conditions andactions. Conditions provide the flexibility to handle different types ofsource images. Conditions and actions come up with associated scripts.In at least some cases, this involves a two-step process. The customerapproves the valid set of rules for his or her data center andbootstraps the Adjustment Orchestrator 4304 and/or 4310 (see also4012-4016) with the rules. The tool allows migration engineers toexecute the standardization in conformance with the rules. A log ismaintained to audit the standardization process any later time.Furthermore, in one or more embodiments, snapshots are employed to allowrollback to a reliable version of the image in case of standardizationfailures. In some embodiments, at least a two-step process is employed;however, in certain cases a multiple step process is utilized. Thecustomer may define a set of migration rules and the migration engineermay provide feedback that some rules cannot be enforced and thus, therecould be an iterative back-and-forth.

The following is an exemplary, illustrative rule set that may be used inthe reliable standardization process described just above:

-   -   If (Cygwin not installed) Then (Install Cygwin)    -   If (ITM (IBM Tivoli Monitoring software, available form        International Business Machines Corporation, Armonk, N.Y., USA)        is present) Then (Uninstall ITM)    -   If (True) Then (Insert ssh keys)    -   If (Symantec Antivirus is not present) Then (Install Symantec        Antivirus)    -   If (Password Expiration=90 days) Then (Set Password        Expiration=180 days)    -   If (Patch X not present) Then (Deploy Patch X) (Patch X here        represents any needed patch; a non-limiting example could be,        for example, Microsoft Patch MS08-067)    -   If (TEM agent not registered) Then (Register TEM Agent)

Refer now to FIG. 42. At 4202, mount the imported image. In step 4224,carry out access enablement; for example:

-   -   1. Add Cygwin SSHD (OpenSSH=sshd) for Windows;    -   2. Add SSH keys;    -   3. Set IP addresses and default gateway to all network        interfaces on first boot;    -   4. Set name server entries; and    -   5. Take a snapshot.

In the event of any failure, as seen at 4204, fix the errors, rollback,and retry. Once all steps are successful, whether on the first attemptor a subsequent re-try, as seen at 4206, start the VM. Then implement anagent un-install procedure 4226; for example:

-   -   1. Uninstall TEM agent    -   2. Uninstall EMC Networker (available from EMC Corporation,        Hopkinton, Mass., USA)    -   3. Uninstall TSM client (IBM Tivoli Storage Manager (TSM)        software available from International Business Machines        Corporation, Armonk, N.Y., USA)    -   4. Uninstall TSCM agent (IBM Tivoli Security Compliance Manager        (TSCM) software available from International Business Machines        Corporation, Armonk, N.Y., USA)    -   5. Uninstall TAD4D agent (Tivoli Asset Discovery for        Distributed, available from International Business Machines        Corporation, Armonk, new York, USA)    -   6. Uninstall ITM agent (IBM Tivoli Monitoring software,        available form International Business Machines Corporation,        Armonk, N.Y., USA)    -   7. Take snapshot

In the event of any failure, as seen at 4208, fix the errors, rollback,and retry. Once all steps are successful, whether on the first attemptor a subsequent re-try, as seen at 4210, proceed to the agent installprocess 4228; for example:

-   -   1. Install TEM    -   2. Set Domain Name System (DNS) Cache Manual

In the event of any failure, as seen at 4212, fix the errors, rollback,and retry. Once all steps are successful, whether on the first attemptor a subsequent re-try, as seen at 4214, proceed to the patching process4230; for example:

-   -   1. Patch to baseline    -   2. Take snapshot

In the event of any failure, as seen at 4216, fix the errors, rollback,and retry. Once all steps are successful, whether on the first attemptor a subsequent re-try, as seen at 4218, proceed to the complianceprocess 4232; for example:

-   -   1. Set Minimum Password Length;    -   2. Set Password History Count    -   3. Set Maximum Password Age    -   4. Set Minimum Password Age    -   5. Set Password Complexity    -   6. Take a snapshot.

In the event of any failure, as seen at 4220, fix the errors, rollback,and retry. Once all steps are successful, whether on the first attemptor a subsequent re-try, as seen at 4222, proceed to the on-boardingprocess.

FIG. 43 shows exemplary standardization architecture. Included areadjustment engine 4302 (which may be provided as a graphical userinterface or GUI or a set of APIs to a master choreographer); and onlineand offline adjustment orchestrators 4304, 4310, respectively (both ofwhich are in the form of components). Other components includeadjustment database 4306, adjustment plan maintenance module 4308,access manager 4312, compliance manager 4316, backup manager 4318,script execution manager 4320, and patch manager 4322. Engine 4302invokes the online and offline adjustment orchestrators 4304, 4310.These in turn query adjustment database 4306, which is maintained byusing adjustment plan maintenance module 4308. The adjustment planmaintenance component is used by the migration team in consultation withthe customer to create an adjustment plan in advance. This plan containsall the rules to guide the adjustment process.

Offline adjustment orchestrator 4310 uses access manager 4312 to providerequired access and interfaces.

Online adjustment orchestrator 4304 invokes compliance manager 4316,backup manager 4318, and script execution manager 4320. Compliancemanager 4316 also invokes script execution manager 4320. Onlineadjustment orchestrator 4304 uses patch manager 4322.

Attention should now be given to FIGS. 44-46, which show exemplarydetailed steps in an adjustment phase. Each step is shown in a “swimlane” indicating what module or entity carries out the particular stepin the exemplary embodiment. Please note that elements 4402, 4408 (cloudportal), and 4410 are not needed for the process depicted in FIG. 44 butare included for illustrative purposes. Migration team 4404 captures allactivities performed by the migration team. This includes activitiesthat are performed by using the Adjustment GUI or invoking theAdjustment APIs as well as manual steps to check for success andfailure. Test and Troubleshoot VM steps 4432, 4442 represent a manualprocess in the example of FIG. 44. The remaining steps are typicallyautomated and involve clicking a button on the portal or calling an API.The entities include the TSAM (IBM Tivoli® Service Automation Managersoftware available from International Business Machines Corporation,Armonk, N.Y., USA) administrator 4402, migration team 4404, VMwarevSphere Virtualization Manager 4406, Portal 4408, TSAM 4410, and back-uplibrary 4412. Processing begins at 4420. In step 4422, carry out smoketesting (i.e., a process of validating code changes before the changesare checked into the product's source tree). In step 4424, back up theVM in question; in step 4426, check same into the back-up library. Instep 4428, the hypervisor provides the VM; in step 4430, configure theVM. Step 4430 is analogous to step 4224 in FIG. 42. In step 4432, testand troubleshoot the VM. In step 4434, back up the configured and testedVM; in step 4436, check same into the back-up library. In step 4428, thehypervisor provides the configured and tested VM; in step 4440 removeinappropriate software and/or agents. Step 4440 is analogous to step4226 in FIG. 42. In step 4442, test and troubleshoot the updated VM withthe inappropriate software and/or agents removed. Processing continuesat 4444.

In FIG. 45, processing begins at point 4446 (which is identical to point4444). In step 4448, back up the updated VM with the inappropriatesoftware and/or agents removed; in step 4450, check same into theback-up library. In step 4452, the hypervisor provides the updated VMwith the inappropriate software and/or agents removed; in step 4454install appropriate agents. Step 4454 is analogous to step 4228 in FIG.42. In step 4456, test and troubleshoot the updated VM with theappropriate agents installed. In step 4458, back up the updated VM withthe appropriate agents installed; in step 4460, check same into theback-up library. In step 4462, the hypervisor provides the updated VMwith the appropriate agents installed; in step 4464 install patches.Step 4464 is analogous to step 4230 in FIG. 42.

In step 4466, test and troubleshoot the updated VM with the patchesinstalled. In decision block 4468, determine if the testing wassuccessful; if yes, at 4470, proceed to the flow in FIG. 46; if no, at4472, fix errors, rollback, and retry, as at 4216 in FIG. 42. In FIG.46, processing begins at point 4474 (which is identical to point 4470).In step 4476, back up the updated VM with the patches installed; in step4478, check same into the back-up library. In step 4480, the hypervisorprovides the updated VM with the patches installed; in step 4482 ensurecompliance. Step 4482 is analogous to step 4232 in FIG. 42. In step4484, test and troubleshoot the post-compliance-check VM. In decisionblock 4486, determine if the testing was successful; if yes, at 4488,proceed with on-boarding; if no, at 4490, fix errors, rollback, andretry, as at 4220 in FIG. 42. In general, in case of errors, roll backto any backup step in the flow is possible.

FIG. 47 shows an exemplary architecture, to assist the skilled artisanin understanding an exemplary system in a pertinent context. One or moreadjustments 4702 are carried out to standardize an arbitrary customerinstance. Prior to attempting adjustments, it is preferable to place asnapshot in a suitable image library such as IBM Tivoli Image Library4718. This can be carried out, for example, using hypertext transferprotocol (http) on port 9443 using IBM Tivoli Image Library. Referencecan be had to scope database 4704 to access pertinent data regarding VMsand applications, and to determine the status of VMs. This can becarried out, for example, using Java Database Connectivity (JDBC). Theimage to be adjusted is mounted in the network file system (NFS) storage4706. Any required VM actions are carried out by cloud vCenter 4710,controlled, by vCenter driver 4712; this results in creation and/ormodification of VMs in cloud 4708 which are in turn mounted in NFSstorage 4706.

An IBM Tivoli® Endpoint Manager (TEM) server 4716 may be employed formigration purposes; communication with same may be had, for example, viatransfer control protocol (tcp). The TEM controls VM patching for thecloud managed environment 4714 in which adjusted VMs reside;communication can be via http or User Datagram Protocol (udp). TEM 4716communicates with Internet 4720 via http on port 80.

One or more embodiments thus provide a system and method to adjustimages so that they meet the image standard of a managed environment4714 and can be managed using standard processes and tools. In one ormore embodiments, such a system includes one or more adjustment typeorchestrators 4012, 4014, 4016 handling specific types of adjustments;an adjustment plan 4018 capturing all the adjustments; and an adjustmentplan maintenance component 4010.

Non-limiting examples of orchestrators include an Access EnablementOrchestrator 4224 to ensure that all source images can be accessed byall relevant management entities (including other orchestrators); anUninstall Orchestrator 4226 to uninstall unwanted software; an installorchestrator 4228 to install required software; a Patch Orchestrator4230 to ensure patch standardization; and a compliance orchestrator 4232to ensure compliance with one or more cloud standards. Differentembodiments could include additional orchestrators, fewer orchestrators,or precisely the orchestrators just described, for example.

The managed environment 4714 may be, for example, an MIaaS cloud (e.g.,IBM SCE+).

The orchestrators may operate on file system virtual machine images(e.g., in image repository 4028) or on VM instances 4030, 4032, 4034.

In some cases, the actions executed by each of the orchestrators aredetermined by a rule engine. Furthermore in this regard, the rule engineis not shown explicitly in the figures to avoid clutter; however, in oneor more embodiments a rule evaluation engine is implicitly implementedin each orchestrator, which needs to evaluate each condition and executethe action only if the condition is satisfied. In some cases, such arule engine includes a set of condition-action pairs (e.g., If (Cygwinnot installed) Then (Install Cygwin) and so on, as discussed above); insuch cases, the action is executed only when the condition is satisfied.In some cases, new rules can be injected in the rule engine to extendthe tool for dealing with new kinds of customer images; for example,such rules can be injected by an adjustment plan maintenance componentsuch as plan manager 4010, which allows for creation, editing, and/ordeletion of rules.

In at least some cases, the overall adjustment flow can be tuned bychanging the adjustment plan 4018 and/or changing the order of theorchestrators 4012-416 or 4224-632.

Recapitulation

Given the discussion thus far, it will be appreciated that, in generalterms, an exemplary method, according to an aspect of the invention,includes the step transferring an arbitrary customer instance(generally, one or more such instances) from a customer environment to atarget infrastructure-as-a-service cloud environment (4714; FIG. 3) as a(generally, one or more) transferred image. “Transferring” should bebroadly understood to include acts by the provider of theinfrastructure-as-a-service cloud environment and/or acts by thecustomer. This step can be carried out, for example, by a transfer corecomponent (e.g., a module 42 in the target infrastructure-as-a-servicecloud environment configured to obtain the arbitrary customer instancefrom a customer environment). A further step includes formulating animage adjustment plan 4018 capturing at least one adjustment required torender the transferred image(s) compliant with standards of the targetinfrastructure-as-a-service cloud environment. “Formulating” should bebroadly understood to include acts performed solely by a machine (e.g.,storing instructions, input by a human, which codify the plan) or actsby both a machine and a human. This step can be carried out, forexample, by adjustment plan maintenance component 4010. A further stepincludes executing the image adjustment plan to adjust the transferredimage(s) to obtain an adjusted image compliant with standards of thetarget infrastructure-as-a-service cloud environment. This step can becarried out by an orchestration component; e.g., choreographer 4008 andone or more orchestrators 4012-4016. A still further step includeson-boarding the adjusted image(s) into the infrastructure-as-a-servicecloud environment as a standard image thereof (generally, one or morestandard image(s)). “Standard” implies that the image then works in thesame manner as if it had been made from the systems own “goldenmasters.” This step can be carried out, for example, by cloud managementlayer 64.

In some cases, the transferred image is adjusted online while running asan instance in the infrastructure-as-a-service cloud environment (e.g.,4030, 4032, 4034). In such cases, the executing step includes executingthe image adjustment plan with an automated framework including at leastone online orchestrator 4304 interacting with the instance in theinfrastructure-as-a-service cloud environment.

In some cases, the transferred image is adjusted offline in a filesystem 4028 of the infrastructure-as-a-service cloud environment. Insuch cases, the executing step includes executing the image adjustmentplan with an automated framework including at least one offlineorchestrator interacting 4310 with the transferred image in the filesystem of the infrastructure-as-a-service cloud environment.

In some cases, the executing step includes executing the imageadjustment plan with an automated framework including at least oneorchestrator interacting with a virtualization manager 4026 (and/orsupporting tools 4004) of the infrastructure-as-a-service cloudenvironment.

In at least some embodiments, the infrastructure-as-a-service cloudenvironment includes a managed infrastructure-as-a-service cloudenvironment having a management layer 64. In such cases, in at leastsome instances, a further step includes managing the standard image withthe management layer together with at least one application created froma managed infrastructure-as-a-service cloud environment applicationgolden master (i.e., an application created from a golden masterassociated with the managed infrastructure-as-a-service cloudenvironment; not meant to imply that it is somehow a golden master ofthe whole cloud environment).

In some embodiments, the image adjustment plan is executed with anautomated framework including at least one of an access enablementorchestrator 4224 which ensures that the adjusted image can be accessedby a management layer of the target infrastructure-as-a-service cloudenvironment; an agent uninstall orchestrator 4226 which uninstallsunwanted software from the transferred image; an agent installorchestrator 4228 which installs required software to the transferredimage; a patching orchestrator 4230 which ensures that the adjustedimage has installed thereon patches required by the standards of thetarget infrastructure-as-a-service cloud environment; and a complianceorchestrator 4232 which ensures that the adjusted image conforms to thestandards of the target infrastructure-as-a-service cloud environment.

In some cases, the executing step includes executing the imageadjustment plan with an automated framework by using an accessenablement orchestrator 4224 to ensure that the adjusted image can beaccessed by a management layer of the target infrastructure-as-a-servicecloud environment; using an agent uninstall orchestrator 4226 touninstall unwanted software from the transferred image; using an agentinstall orchestrator 4228 to install required software to thetransferred image; using a patching orchestrator 4230 to ensure that theadjusted image has installed thereon patches required by the standardsof the target infrastructure-as-a-service cloud environment; and using acompliance orchestrator 4232 to ensure that the adjusted image conformsto the standards of the target infrastructure-as-a-service cloudenvironment.

In some cases, adjustment plan 4018 includes rules that uniformly encodeadjustment recipes across different kinds of images. Preferably butoptionally, the orchestration framework is generic and can deal withmultiple types of adjustment actions. In at least some cases, theadjustment orchestrator(s) define(s) a set of phases with steps in eachphase encapsulated in a script. Such scripts may run in an adjustmentengine and may target VMs 4030-4034, management tools 4020-4024, or thelike. Some techniques adjust multiple images in parallel. In some cases,the adjustment orchestrator(s) is/are bootstrapped with rules. Theactions of the orchestrators are determined by a rule engine (a set ofcondition/action pairs); new rules can be injected by adjustment planmaintenance component 4010. The adjustment flow can be changed bychanging the plan and/or changing the order of the orchestrators. Theframework can be extended by adding and/or registering a new actionand/or orchestrator to an existing plan.

In another aspect, an exemplary apparatus includes a memory (e.g., RAM28, cache 32); at least one processor 16, coupled to the memory; and anon-transitory computer-readable storage medium 34, embodying in anon-transitory manner a plurality of distinct software modules 42. Theplurality of distinct software modules in turn include an adjustmentplan maintenance component module 4010 including instructions which,when loaded into the memory, configure the at least one processor toformulate an image adjustment plan 4018 capturing at least oneadjustment required to render a transferred image compliant withstandards of a target infrastructure-as-a-service cloud environment. Thetransferred image includes an arbitrary customer instance from acustomer environment. Also included are an adjustment orchestrationmodule (e.g., 4008 and 4012-4016) including instructions which, whenloaded into the memory, configure the at least one processor to executethe image adjustment plan to adjust the transferred image to obtain anadjusted image compliant with standards of the targetinfrastructure-as-a-service cloud environment; and a cloud managementmodule 64 including instructions which, when loaded into the memory,configure the at least one processor to on-board the adjusted image intothe infrastructure-as-a-service cloud environment as a standard imagethereof.

In some cases, the adjustment orchestration module includes instructionswhich, when loaded into the memory, configure the at least one processorto adjust the transferred image online while running as an instance inthe infrastructure-as-a-service cloud environment, as at 4030-4034. Insome cases, the adjustment orchestration module includes instructionswhich, when loaded into the memory, configure the at least one processorto adjust the transferred image offline in a file system 4028 of theinfrastructure-as-a-service cloud environment.

In some embodiments, the adjustment orchestration module includesinstructions which, when loaded into the memory, configure the at leastone processor to interact with a virtualization manager 4026 of theinfrastructure-as-a-service cloud environment. In some embodiments, theadjustment orchestration module includes instructions which, when loadedinto the memory, configure the at least one processor to interact with asupporting tool 4020-4024 of the infrastructure-as-a-service cloudenvironment.

In at least some cases, the infrastructure-as-a-service cloudenvironment includes a managed infrastructure-as-a-service cloudenvironment 4714 having a management layer 64. The management layer can,for example, manage the standard image together with at least oneapplication created from a managed infrastructure-as-a-service cloudenvironment application golden master.

In some embodiments, the adjustment orchestration module includes anadjustment choreographer 4008 and at least one of: an access enablementorchestrator 4224 which ensures that the adjusted image can be accessedby a management layer of the target infrastructure-as-a-service cloudenvironment; an agent uninstall orchestrator 4226 which uninstallsunwanted software from the transferred image; an agent installorchestrator 4228 which installs required software to the transferredimage; a patching orchestrator 4230 which ensures that the adjustedimage has installed thereon patches required by the standards of thetarget infrastructure-as-a-service cloud environment; and a complianceorchestrator 4232 which ensures that the adjusted image conforms to thestandards of the target infrastructure-as-a-service cloud environment.

In some cases, the adjustment orchestration module includes anadjustment choreographer 4008; an access enablement orchestrator 4224which ensures that the adjusted image can be accessed by a managementlayer of the target infrastructure-as-a-service cloud environment; anagent uninstall orchestrator 4226 which uninstalls unwanted softwarefrom the transferred image; an agent install orchestrator 4228 whichinstalls required software to the transferred image; a patchingorchestrator 4230 which ensures that the adjusted image has installedthereon patches required by the standards of the targetinfrastructure-as-a-service cloud environment; and a complianceorchestrator 4232 which ensures that the adjusted image conforms to thestandards of the target infrastructure-as-a-service cloud environment.

Exemplary System and Article of Manufacture Details

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely software embodiment (including firmware, residentsoftware, micro-code, etc.) or an embodiment combining software andhardware aspects that may all generally be referred to herein as a“circuit,” “module” or “system.” Furthermore, aspects of the presentinvention may take the form of a computer program product embodied inone or more computer readable medium(s) having computer readable programcode embodied thereon. In some cases, some aspects of the invention maybe implemented in hardware in an appliance that a migration team bringsinto a customer environment.

One or more embodiments of the invention, or elements thereof, can beimplemented in the form of an apparatus including a memory and at leastone processor that is coupled to the memory and operative to performexemplary method steps.

One or more embodiments can make use of software running on a generalpurpose computer or workstation. With reference to FIG. 1, such animplementation might employ, for example, a processor 16, a memory 28,and an input/output interface 22 to a display 24 and external device(s)14 such as a keyboard, a pointing device, or the like. The term“processor” as used herein is intended to include any processing device,such as, for example, one that includes a CPU (central processing unit)and/or other forms of processing circuitry. Further, the term“processor” may refer to more than one individual processor. The term“memory” is intended to include memory associated with a processor orCPU, such as, for example, RAM (random access memory) 30, ROM (read onlymemory), a fixed memory device (for example, hard drive 34), a removablememory device (for example, diskette), a flash memory and the like. Inaddition, the phrase “input/output interface” as used herein, isintended to contemplate an interface to, for example, one or moremechanisms for inputting data to the processing unit (for example,mouse), and one or more mechanisms for providing results associated withthe processing unit (for example, printer). The processor 16, memory 28,and input/output interface 22 can be interconnected, for example, viabus 18 as part of a data processing unit 12. Suitable interconnections,for example via bus 18, can also be provided to a network interface 20,such as a network card, which can be provided to interface with acomputer network, and to a media interface, such as a diskette or CD-ROMdrive, which can be provided to interface with suitable media.

Accordingly, computer software including instructions or code forperforming the methodologies of the invention, as described herein, maybe stored in one or more of the associated memory devices (for example,ROM, fixed or removable memory) and, when ready to be utilized, loadedin part or in whole (for example, into RAM) and implemented by a CPU.Such software could include, but is not limited to, firmware, residentsoftware, microcode, and the like.

A data processing system suitable for storing and/or executing programcode will include at least one processor 16 coupled directly orindirectly to memory elements 28 through a system bus 18. The memoryelements can include local memory employed during actual implementationof the program code, bulk storage, and cache memories 32 which providetemporary storage of at least some program code in order to reduce thenumber of times code must be retrieved from bulk storage duringimplementation.

Input/output or I/O devices (including but not limited to keyboards,displays, pointing devices, and the like) can be coupled to the systemeither directly or through intervening I/O controllers.

Network adapters 20 may also be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems orremote printers or storage devices through intervening private or publicnetworks. Modems, cable modem and Ethernet cards are just a few of thecurrently available types of network adapters.

As used herein, including the claims, a “server” includes a physicaldata processing system (for example, system 12 as shown in FIG. 1)running a server program. It will be understood that such a physicalserver may or may not include a display and keyboard.

As noted, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon. Anycombination of one or more computer readable medium(s) may be utilized.The computer readable medium may be a computer readable signal medium ora computer readable storage medium. A computer readable storage mediummay be, for example, but not limited to, an electronic, magnetic,optical, electromagnetic, infrared, or semiconductor system, apparatus,or device, or any suitable combination of the foregoing. More specificexamples (a non-exhaustive list) of the computer readable storage mediumwould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(RAM), a read-only memory (ROM), an erasable programmable read-onlymemory (EPROM or Flash memory), an optical fiber, a portable compactdisc read-only memory (CD-ROM), an optical storage device, a magneticstorage device, or any suitable combination of the foregoing. In thecontext of this document, a computer readable storage medium may be anytangible medium that can contain, or store a program for use by or inconnection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. In the most general case, the program code mayexecute entirely on the user's computer, partly on the user's computer,as a stand-alone software package, partly on the user's computer andpartly on a remote computer or entirely on the remote computer orserver. In the latter scenario, the remote computer may be connected tothe user's computer through any type of network, including a local areanetwork (LAN) or a wide area network (WAN), or the connection may bemade to an external computer (for example, through the Internet using anInternet Service Provider). However, one or more embodiments areparticularly significant in the context of a cloud or virtual machineenvironment. Reference is made back to FIGS. 1-3 and accompanying text.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

It should be noted that any of the methods described herein can includean additional step of providing a system comprising distinct softwaremodules embodied on a computer readable storage medium; the modules caninclude, for example, any or all of the appropriate elements depicted inthe block diagrams in any of the pertinent figures and/or describedherein; by way of example and not limitation, any one, some or all ofthe modules/blocks and or sub-modules/sub-blocks in FIGS. 16-19, such asa discovery tool module to carry out functionality 16100 (optionallywith sub-modules to carry out 16110, 16120, 16130, and/or 16140), adescription module to hold description 16300 (optionally withsub-data-structures for data 16310, 16320, 16330, and/or 16340), and aninfrastructure comparison engine module 16200 (optionally withsub-modules to implement functionality 16210, 16220, 16230, and/or16240). The customer environment 1702 may have one or more modules toimplement one or more transfer agents and/or may have some or all of thediscovery tool functionality as discussed elsewhere. The method stepscan then be carried out using the distinct software modules and/orsub-modules of the system, as described above, executing on one or morehardware processors such as 16. Further, a computer program product caninclude a computer-readable storage medium with code adapted to beimplemented to carry out one or more method steps described herein,including the provision of the system with the distinct softwaremodules.

In any case, it should be understood that the components illustratedherein may be implemented in various forms of hardware, software, orcombinations thereof; for example, application specific integratedcircuit(s) (ASICS), functional circuitry, one or more appropriatelyprogrammed general purpose digital computers with associated memory, andthe like. Given the teachings of the invention provided herein, one ofordinary skill in the related art will be able to contemplate otherimplementations of the components of the invention.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method comprising: discovering, in a sourcecomputing system having a source management infrastructure, at least onesource infrastructure management component, wherein said at least onesource infrastructure management component is an instance of an image,and wherein said at least one source infrastructure management componentis running in a customer environment; querying a database to obtain adescription of a target cloud infrastructure; analyzing said at leastone source infrastructure management component using said description ofsaid target cloud infrastructure to determine that said at least onesource infrastructure management component is appropriate forinfrastructure configuration mapping to said target cloudinfrastructure; stopping an application executing on said at least onesource infrastructure management component determined appropriate forinfrastructure configuration mapping; and capturing said at least onesource infrastructure management component determined appropriate forinfrastructure configuration mapping for migration to said target cloudinfrastructure.
 2. The method of claim 1, wherein, in said discoveringstep, said at least one source infrastructure management componentcomprises at least one of: at least one source infrastructure managementclient; at least one source infrastructure management server; at leastone source infrastructure management configuration; and at least onesource infrastructure management log.
 3. The method of claim 2, furthercomprising deriving a description of non-functional requirements of saidsource management infrastructure.
 4. The method of claim 3, wherein: insaid discovering step, said at least one source infrastructuremanagement component comprises at least: said at least one sourceinfrastructure management configuration; and said at least one sourceinfrastructure management log; in said querying step, said descriptionof said target cloud infrastructure comprises at least one of: cloudinfrastructure software standards; cloud infrastructure softwareconfigurations; and a description of non-functional requirements of atarget management infrastructure of said target cloud infrastructure;said analyzing comprises: matching said cloud infrastructure softwarestandards with at least a corresponding one of: said at least one sourceinfrastructure management client; and said at least one sourceinfrastructure management server; mapping said description of saidnon-functional requirements of said source management infrastructurewith said description of said non-functional requirements of said targetmanagement infrastructure; and mapping said cloud infrastructuresoftware configurations with said at least one source infrastructuremanagement configuration and said at least one source infrastructuremanagement log.
 5. The method of claim 4, wherein said mapping of saidcloud infrastructure software configurations with said at least onesource infrastructure management configuration and said at least onesource infrastructure management log is at least partially based on:said matching of said cloud infrastructure software standards with saidat least one source infrastructure management client and said at leastone source infrastructure management server; and said mapping of saiddescription of said non-functional requirements of said sourcemanagement infrastructure with said description of said non-functionalrequirements of said target management infrastructure.
 6. The method ofclaim 5, wherein: in said discovering step, said at least one sourceinfrastructure management component further comprises at least onesource infrastructure management process; in said querying step, saiddescription of said target cloud infrastructure further comprises atleast one target infrastructure management process; and said analyzingfurther comprises mapping said at least one source infrastructuremanagement process with said at least one target infrastructuremanagement process.
 7. The method of claim 6, wherein said mapping ofsaid at least one source infrastructure management process with said atleast one target infrastructure management process is at least partiallybased on said mapping of said description of said non-functionalrequirements of said source management infrastructure with saiddescription of said non-functional requirements of said targetmanagement infrastructure.
 8. The method of claim 2, wherein: in saidquerying step, said description of said target cloud infrastructurecomprises at least one of: cloud infrastructure software standards; andcloud infrastructure software configurations; said analyzing comprises:matching said cloud infrastructure software standards with at least acorresponding one of: said at least one source infrastructure managementclient; and said at least one source infrastructure management server;and mapping said cloud infrastructure software configurations with saidat least one source infrastructure management configuration.
 9. Themethod of claim 8, wherein said mapping of said cloud infrastructuresoftware configurations with said at least one source infrastructuremanagement configuration is at least partially based on said matching ofsaid cloud infrastructure software standards with said at least onesource infrastructure management client and said at least one sourceinfrastructure management server.
 10. The method of claim 9, wherein: insaid discovering step, said at least one source infrastructuremanagement component further comprises at least one sourceinfrastructure management process; in said querying step, saiddescription of said target cloud infrastructure further comprises atleast one target infrastructure management process; and said analyzingfurther comprises mapping said at least one source infrastructuremanagement process with said at least one target infrastructuremanagement process.
 11. The method of claim 1, wherein said analyzingstep further comprises determining that at least one conflict existswith said at least one mandatory target infrastructure managementcomponent, wherein said at least one conflict comprises said at leastone source infrastructure management component managing at least oneobject that said at least one mandatory target infrastructure managementcomponent will manage in said target cloud infrastructure.
 12. Themethod of claim 1, wherein said analyzing step further comprisesdetermining that at least one conflict exists with said at least onemandatory target infrastructure management component, wherein said atleast one conflict comprises said at least one source infrastructuremanagement component using at least one resource that said at least onemandatory target infrastructure management component will use in saidtarget cloud infrastructure.
 13. The method of claim 1, wherein saidanalyzing step further comprises determining that at least one conflictexists with said at least one mandatory target infrastructure managementcomponent, wherein said at least one conflict comprises at least one of:current lack of a mandatory target infrastructure component on a client,existence of a mandatory target infrastructure component in a differentversion, and existence of a mandatory target infrastructure componentwith different configurations.
 14. The method of claim 1, wherein saidanalyzing comprises at least one of: recommending un-installation of asource infrastructure component; recommending installation of a targetinfrastructure component; recommending modifying configuration of aninfrastructure component; and recommending excluding servers with agiven source infrastructure component from migration.
 15. The method ofclaim 1, wherein: said discovering comprises discovering, in said sourcecomputing system, a plurality of source infrastructure managementcomponents; and said analyzing comprises: initially aggregating all ofsaid plurality of source infrastructure management components;developing generic recommendations for said aggregated plurality ofsource infrastructure management components; applying saidrecommendations on a per-instance basis; and refining at least some ofsaid applied recommendations in cases where said generic recommendationsare inconclusive.
 16. The method of claim 1, wherein said discovering iscarried out on at least one physical machine in said source computingsystem, said at least one physical machine comprising a client of saidat least one source infrastructure management component.
 17. The methodof claim 1, wherein said discovering is carried out on at least onephysical machine in said source computing system, said at least onephysical machine comprising a server on which said at least one sourceinfrastructure management component runs.
 18. The method of claim 1,further comprising providing a system, wherein the system comprisesdistinct software modules, each of the distinct software modules beingembodied on a non-transitory computer-readable storage medium, andwherein the distinct software modules comprise a discovery tool module,a description module, and an infrastructure comparison engine module;wherein: said discovering is carried out by said discovery tool moduleexecuting on at least one hardware processor; said querying is carriedout by said description module executing on said at least one hardwareprocessor; and said analyzing is carried out by said infrastructurecomparison engine module executing on said at least one hardwareprocessor.
 19. A method comprising: discovering, in a source computingsystem having a source management infrastructure, at least one sourceinfrastructure management component, wherein said at least one sourceinfrastructure management component is an instance of an image, andwherein said at least one source infrastructure management component isrunning in a customer environment; querying a database to obtain adescription of a target cloud infrastructure; analyzing said at leastone source infrastructure management component using said description ofsaid target cloud infrastructure to determine that said at least onesource infrastructure management component is appropriate forinfrastructure configuration mapping to said target cloudinfrastructure, wherein: in said discovering step, said at least onesource infrastructure management component comprises at least one of: atleast one source infrastructure management client; at least one sourceinfrastructure management server; at least one source infrastructuremanagement configuration; and at least one source infrastructuremanagement log; in said querying step, said description of said targetcloud infrastructure comprises at least one of: cloud infrastructuresoftware standards; and cloud infrastructure software configurations;said analyzing comprises: matching said cloud infrastructure softwarestandards with at least a corresponding one of: said at least one sourceinfrastructure management client; and said at least one sourceinfrastructure management server; and mapping said cloud infrastructuresoftware configurations with said at least one source infrastructuremanagement configuration determined appropriate for infrastructureconfiguration mapping.